Why does THG have an article titled "XP For Hardware" that hardly talks considerably more about the software side of XP and actually doesn't answer any of my questions about how XP handles hardware at all?
Confused minds want to know.
-Intelicide: The act of marketing overriding engineers to kill a product before it can be released.
Oh, I agree. It was just that the title and opening statements didn't in any way match the rest of the article. They could have just titled it, "A preview of Win XP", and I would have been happy.
Though I'm still concerned by any OS requiring that much RAM as a minimum... I guess M$ hasn't ever heard of optimization.
Then again, that's pretty obvious as PowerPoint stores all images in giganto-bitmap format even though they may have been just a tiny gif imported.
-Intelicide: The act of marketing overriding engineers to kill a product before it can be released.
Last I heard, the minimum RAM requirement was 128MB. Which means I'd have to get a system with 256MB just to run any of my software because the OS would already be eating up 128MB of that. Gratned, if I got a new system, my minimum would be 512MB anyway. Still, any software that needs 128MB as a MINIMUM has got some serious memory optimization (or lack thereof) issues.
And the worst part is the more I hear about WinXP, the more options I know I'd turn off if I ever had to use it just because they'd drive me nuts.
-Intelicide: The act of marketing overriding engineers to kill a product before it can be released.
I have used the Beta a little bit and as my brother likes to say "It's the prettiest piece of crap Microsoft has come out with yet." It has some good points but there seem to be a lot of changes that are there just to set it apart from previous versions. But the major debate about XP is the Activation step. The fact that 14 days (I believe 30 or 60 days in the final release) after you install it, it will create a hardware code specific to your computer. You have to send this code to Microsoft and they will "verify" you somehow so that you can continue. So if you change 3 or more devices your hardware code changes and you have to re-verify with Microsoft (on the phone) and explain what you have done to your computer. A real nuisance for people who swap HD's and stuff in and out a lot. Anyways, I believe that the Activation feature and the large amout of debate surrounding it is why the article is worded the way it is.
If you are worried about hardware compatability, all I can say is it detected all of our hardware fine and configured fairly easily.
I have little faith that WinXP could pick up the hardware I have correctly. I seem to have a knack for finding components that are difficult to find drivers for and that Windows often detects incorrectly, if at all. I still haven't found any Windows drivers for my old ThrustMaster Mark II FCS.
So I'd highly doubt that WinXP could detect my hardware properly. Thus I'll need some form of manual control over setting up my hardware. Does WinXP have this? Does it let you remove drivers that Windows has chosen and add your own drivers for your hardware? Does it let you set specific IRQs?
The article didn't cover any of this simple information about how WinXP handles hardware, and these are concerns that I'd really need answering before I'd even consider upgrading.
I'm curious if it wastes resources on old DOS commands. Does it have sound blaster emulation? I personally hope it doesn't (but that you can add it if you want) since I'm sick of having to disable it and get an error on startup each time. I don't use a single dos program.
<font color=red>Yeah, I took a crap on your lawn. Whatcha gonna do about it?</font color=red>
I'd kill to have 100% DOS backward compatability in a Windows product again. I have plenty of old DOS games that won't even run because Microsoft decided to stop supporting some of the Assembler interupts in Windows.
I just don't get it, why would it be so hard to write into Windows a DOS emulator using DirectX where you have a 100% backward compatability, SB16 to DirectX emulation, and a speed adjustment? Then you could run any DOS software under Windows without flaw, and you wouldn't need all of the crappy half-arsed support that is in Windows currently.
I didn't use a PC during the DOS days though. So I think it's a waste. I agree though that it should be able to be added if you want to run old software, but there should be no reason for Windows to install anything DOS related from the get go.
<font color=red>Yeah, I took a crap on your lawn. Whatcha gonna do about it?</font color=red>
With the exception of Microsoft’s stupid licensing and registration crap, I’m very pleased with XP rc2.
I’ve installed it on a couple of systems including components such as:
Adaptec 7780 Dual Channel SCSI
Creative Labs AWE 64
Vortex PCI audio card
Intel BX motherboard
AMD 760 motherboard
Matrox Millennium G200
MSI TNT2 32MB Video
HP 8100I CD-RW
And a bunch of other stuff, both old and new, name brand, and OEM.
XP detected and installed every piece of hardware without prompting me for a driver disk or anything.
I was very pleased with its hardware performance.
Also XP runs just fine even on an old 450HMz PII w/128MB RAM it does slow down a bit when running multiple logins or software emulation, but no problem keeping PhotoShop 6, Word XP, and the internet open.
Yeah, my dad wants run this freakin old dos app for his financing stuff (the actual program is still on one of those 5 1/4" disks!!). So i think i'll make a dos boot-up disk for him just so he can run that ancient program.
<b>Does it work?</b>
Yes!
<b>Ok, How <i>well</i> does it work?</b>
Uhh...
Yeah. Windows shouldn't have DOS functionality anymore. Hardly anyone these days even knows how to do anything in DOS. So I don't have a problem with M$ canning that. However if they do that, they should also make a DOS emulator so that people who do use DOS can still use DOS.
Heck, I'd set up an old system as a purely DOS machine, except that my M$ DOS 6.22 floppies have died. I once tried setting up a dual-boot DOS/Win95b system, only the instructions that I had gotten from M$ failed to mention that minor detail that Win95b natively uses FAT32, so all of my HDs were FAT32 formatted. Thus when it went into DOS mode, it killed everything as DOS only knew FAT16. It took me a while to get that system restored because I was stupid enough to not test my emergency floppy first, which had gone bad. It took taking my system over to a cousin who had working boot floppies to fix that mess.
I miss a lot of my old DOS games. Sure the graphics and sound suck, but they games themself were fun. Heck, EarthSiege 1 was a lot more playable than ES2 ever was.
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.