I have a 20" Dell-branded LCD at work. It runs at 1600x1200, and is probably the single best screen I have ever in my life used. No more eye strain, no more fuzzies, no more excessive heat.
I'm saying that, with respect to civil rights, these states are becoming marginalized. Other states would be free to say, "Don't like South Carolina, come live with us!". Then, South Carolina could degrade into some good-ol-boy all-white hog-molesting pit of human disgrace, and the other states would just laugh at them.
And we would be left supporting them in their hopeless endevour. Not something I want my money going to.
Hard links already exist in NTFS, as well as the "junction points" you speak of. NTFS supports pretty much every feature worth having in a file system. Internally, each file is made up of a bunch of attributes & metadata, including filenames. A file with multiple names is effectively a hard-link. A symbolic link is simply a file with a particular attribute set, and the associated meta-data format specifies what it's linked to.
It uses the exact same subsystem. You draw to a device context, all drawing is done with the same commands. The device context is mapped to a physical device (so your code isn't 100% the same, due to DPI changes, etc) and the driver for said device knows how to interpret the data in the context. Printing under windows is a breeze if you know the basics of the GDI.
Directional and horizontal drilling have been in development for the better part of 20 years. This will be a godsend to them. As it is, the equipment required to transfer control and status data back and forth to the motors is bulky, expensive, and prone to failure.
Most of you don't realize it, but this type of drilling is used all over the place now for all kinds of things. The largest use other than the oil industry is for drilling underneath things (anything, roads, buildings, ship channels, etc) so that cabling, or really damn near anything requiring a hole in the ground can be laid without destruction to the overlying structure. In the early 90's, my dad participated in a project to raise a half-sunken ship from the bottom of a Danish port. They drilled horizontally under the ground beneath the ship, and ran metal cabling underneath it. The cabling was attached to barges on either side of the ship. They pulled apart and raised it off the ocean floor.
If anyone had bothered to read Troll's FAQ on the subject, the "memory" footprint of the system also includes the entire size of the framebuffer memory. A high-res color screen is going to have a fairly large framebuffer, regardless of it being on a PDA or not.
But instead we just get whining that "real programmers" shouldn't use QT for whatever reason.
According to our company's MS contact (we do a lot of windows backup stuff), the API for backing up the windows registry DOES NOT WORK. Microsoft has stated they have NO PLANS TO FIX IT.
The only solution for a complete system backup is to backup all files, and dump the registry to a text file. When you restore the file, import the text file back into the system with regedit.
Well that's just great, build your own damn box. The people that buy Apples, and yes, Dells _don't_. It needs to be kept in mind that not everyone gives a flying fuck about building their own s00per-duper machine with all the bells and whistles, especially when you have to deal with umpteen different manufacturer's warranties.
Man, you would think this web site existed in a vacuum.
The integer unit of the Hitachi SH-4 used in the dreamcast is 64-bit only. However, there is a "vector" unit slapped on it that does 128-bit floating point ops. All this at 200mhz.
Or maybe it was because the powerglove was pretty much a piece of crap, and rarely worked with the hardware it was intended for (NES). Let alone a real PC with some trickery in between.
Slashdot Mirror
And they're still running it all over 133mhz PCI.
It was called IFS and Oracle did it like, almost four years ago.
Versioning and various other metadata existed. It could be exported via SMB, NFS, FTP, and as a regular "local" windows filesystem.
And, why is this such a great big deal? I don't see the same stink raised as the possibility of Longhorn having a DB for a filesystem.
I think it was Louisiana. If you've never been there, it's not surprising.
I have a 20" Dell-branded LCD at work. It runs at 1600x1200, and is probably the single best screen I have ever in my life used. No more eye strain, no more fuzzies, no more excessive heat.
I'm saying that, with respect to civil rights, these states are becoming marginalized. Other states would be free to say, "Don't like South Carolina, come live with us!". Then, South Carolina could degrade into some good-ol-boy all-white hog-molesting pit of human disgrace, and the other states would just laugh at them.
And we would be left supporting them in their hopeless endevour. Not something I want my money going to.
Actually, the earth is an oblique ellipsoid.
Hard links already exist in NTFS, as well as the "junction points" you speak of. NTFS supports pretty much every feature worth having in a file system. Internally, each file is made up of a bunch of attributes & metadata, including filenames. A file with multiple names is effectively a hard-link. A symbolic link is simply a file with a particular attribute set, and the associated meta-data format specifies what it's linked to.
It uses the exact same subsystem. You draw to a device context, all drawing is done with the same commands. The device context is mapped to a physical device (so your code isn't 100% the same, due to DPI changes, etc) and the driver for said device knows how to interpret the data in the context. Printing under windows is a breeze if you know the basics of the GDI.
How hard is that, really?
Directional and horizontal drilling have been in development for the better part of 20 years. This will be a godsend to them. As it is, the equipment required to transfer control and status data back and forth to the motors is bulky, expensive, and prone to failure.
Most of you don't realize it, but this type of drilling is used all over the place now for all kinds of things. The largest use other than the oil industry is for drilling underneath things (anything, roads, buildings, ship channels, etc) so that cabling, or really damn near anything requiring a hole in the ground can be laid without destruction to the overlying structure. In the early 90's, my dad participated in a project to raise a half-sunken ship from the bottom of a Danish port. They drilled horizontally under the ground beneath the ship, and ran metal cabling underneath it. The cabling was attached to barges on either side of the ship. They pulled apart and raised it off the ocean floor.
They're all WASP cowboys. At least there is some diversity (some, ahah, try a LOT) of diversity in Houston.
I have yet to see anything displayed on my PS2 that is any better (or even close, really) to what my Radeon can do.
Hell, it's not even any more impressive than my Dreamcast.
Sarcasm guys,
"I had a hard time _not_ finding the right drivers".
Hehe.
If anyone had bothered to read Troll's FAQ on the subject, the "memory" footprint of the system also includes the entire size of the framebuffer memory. A high-res color screen is going to have a fairly large framebuffer, regardless of it being on a PDA or not.
But instead we just get whining that "real programmers" shouldn't use QT for whatever reason.
According to our company's MS contact (we do a lot of windows backup stuff), the API for backing up the windows registry DOES NOT WORK. Microsoft has stated they have NO PLANS TO FIX IT.
The only solution for a complete system backup is to backup all files, and dump the registry to a text file. When you restore the file, import the text file back into the system with regedit.
Well that's just great, build your own damn box. The people that buy Apples, and yes, Dells _don't_. It needs to be kept in mind that not everyone gives a flying fuck about building their own s00per-duper machine with all the bells and whistles, especially when you have to deal with umpteen different manufacturer's warranties.
Man, you would think this web site existed in a vacuum.
The integer unit of the Hitachi SH-4 used in the dreamcast is 64-bit only. However, there is a "vector" unit slapped on it that does 128-bit floating point ops. All this at 200mhz.
Having just taken a database course a year ago in which we had to deal with a hierarchical database. It is absolutely awful.
Has an upgradeable firmware, and the system is running linux.
That is a function of how your tables / database are setup, rather than the database system it's running under.
Right?
There are several possibilities:
1) Shinobi - the official Sega "OS". It's really
just a mixed low/high level API. Not an OS.
2) Dragon - WinCE for DC. This is crap. Few
people ever used it, though it was the first
winCE with direct-x.
3) Linux - it runs all right.
4) KallistiOS, it's turning back into a library now.
I've got the DC dev kit, and by FAR the Sega API is the best and easiest to use.
Feeling superior because of your OS is pretty lame, regardless of system.
Or maybe it was because the powerglove was pretty much a piece of crap, and rarely worked with the hardware it was intended for (NES). Let alone a real PC with some trickery in between.
Move along now.
You do not have to be a member of anything to drink in Houston.