wilgaa

No need to fret. I have an OEM copy of nLited copy XP Pro sitting on my hd, and I have used it for more than days.... Then again, remember: Be sure to write down the product key that's in the winnt.sif file, NOT the one on the side of the computer. You won't run into the 30-day problem, provided you have the correct oembios.* files and are installing on a system with a matching DMI/SMBIOS string. You'll have to re-enter the key you wrote down (from the winnt.sif) during the setup process.

Hi. I'm having a wild problem with the the WoW32 subsystem's windows 3.1 install. If I run a game that requires installation, and/or has an installer that doesn't explicitly check if you have a video card, the game runs fine. One such game is Entombed, which displays the following message: Entombed has not detected a 256 color display driver. Please use the Windows Setup to select or install a 256 color display driver that supports your video card. Contact the vendor of your video card if you cannot locate or install a 256 color diplsay driver. Entombed will now close. I have tried running it under both Virtual PC and DOSBox, with no success. In DOSBox, I can't get a single video driver to work, even though the S3 driver should work, since it emulates a Trident card. In Virtual PC (which emulates a Trio64), I tried installing the drivers, but upon restarting win3.11, it fails. I have successfully installed SciTech Display Doctor 5.3a in wfw3.11, but it still claims it can't find a driver, because it doesn't show up in winsetup.exe (because the setup prog copies the files itself). When I open winsetup (and point it to the SDD directory), it complains that it can't find any inf files. What do I do? I could theoretically try it under dos (the interated graphics do have a driver for win3.11), but then there would be no sound. I remember going over to a friends house a couple years ago, and looking around the HD. The computer ran win95. After looking around a while, I found out that the computer had the same chipset that sound dsp/codec that mine does. And, to my suprise, their system had both ms-dos and Windows 3.1 drivers. I even remember seeing it load the dos drivers on bootup. In fact, the 95 install actually used win3.11 drivers. So I finally found the setup files on the hd (for both the DOS and win3.1 drivers), and copied the files to some floppies. So it seems like between 1996 and 2000,themobo didn't change that much. My current system has a MEW-AM mobo, and looking through the specs, it says (rather generically ) that it has a Crystal Semiconductor sound chipset". Duh!!! Well that was obvious, so the question is now, what chipset???? :confuzed: So there can only be two possible answers: 1) Tell me how to trick to get 256 color mode working for WoW apps. 2) Or if you can't 'trick' it, can you even run apps that require more than 16 colors in the WoW subsystem, and if so, how??? 3) Point me to a dos driver for the sound card, or at least tell me the dang chipset. The documentation sucks. Any help would be appreciated.

Win XP...and yes, and mini-windows install (from a hard drive) Have a look at the attachments to see that is indeed complete...for a minimal system, that is

Hi. I'm stuck. I'm trying to shrink my windows installation to that of mindows. I first started by copying my entire system32 directory to c:\mini, including the config directory. However, after loading the registry hive and changing the %systemroot% variable to 'C:\MINI', I receive the 'registry is corrupted...' message. And this is after after I had changed all the 'C:\WINNT' entries to 'C:\MINI'. To recap, and to be more specific, I did the following: 1) Copied all the files in C:\WINNT\SYSTEM32 to C:\MINI\SYSTEM32 2) Opened the registry editor. 3) Selected the HKLM key, and loaded the C:\MINI\SYSTEM32\CONFIG\SYSTEM hive under the 'a' key. 4) Closed the registry editor. 5) Used a bulk find/replace registry utility to change all of the 'C:\WINNT\...' entries to 'C:\MINI...'. 6) Repeated steps 2-5 for the remaining hives. 7) Edited boot.ini to add C:\MINI as a boot option. 8) Rebooted. 9) Booted the new entry. 10) Received the 'Your registry is corrupt...' message. 11) Tried again with the '/minint' and '/winpe' switches, both alone and together. Same error. 12) Using Process Explorer, managed to reduce the number of files to 354 files. 13) Tried again, received same message. 14) Edited hive, set 'SystemSetupInProgress' to '1'. 15) Renamed setup.exe to setup.old (in 'mini' system32). 16) Copied cmd.exe to setup.exe. 17) Tried again. Same error. 18) Deleted the config directory. 19) Copied the C:\WINNT\SYSTEM32\CONFIG\*.sav files to C:\MINI\SYSTEM32\CONFIG. 20) removed the '.sav' extension. 21) Tried again. Received the infamous 'hal.dll missing...' message. 22) Imported mini 'SOFTWARE' hive under the 'a' key. 23) Navigated to 'HKLM/a/Microsoft/Windows NT/CurrentVersion'. 24) Tried to create a new REG_SZ value named 'SystemRoot'. Failed with message 'Cannot create value. Error writing to registry.' 25) Tried again, only this time choosing a 'dollar' value for the key (ex: '$a$'). Didn't work. 26) Tried creating any key/value of any type under the imported hive. Didn't work. For reference, I have attached the listing of the system32 directory (min.txt) and 'old' directory (the one that has the files that I removed to get it down to >400 files (del.txt). Hope this helps. min.txt del.txt

OK....Let's face it---people lose things. With that out of the way, on to the question... I have a Win2k pro CD that I bought in 2000 (heh). However, I have lost the piece of paper that has the product key on it (on the back, under the CD tray). Can I call Microsoft, and ask them to look up the product key that I registered with, and then give me the key? As for verification (that this is a legitimate copy), could I: * give them the serial number of the CD (that's printed on the top-center of the disc * read them the info as reported by a CD info utility (suck as Nero's InfoTool) Thanks, any help would be appreciated.

Sorry to hear that Why did it die? Please give a reason (bad capacitors, etc). Also, who is the manufacturer? If it's Asus, my advice would be: Don't buy Asus mobos!!!! LOL. I have a Gateway, so how funny is that? Um, just take the hard drive out and put it in another PC. Problem solved. If it's an Asus mobo, forget about it. They have the worst support. Period. Also, If you don't get the board fixed (or a least a new one), avoid Sony at all costs. Trust me, their support is worse than Asustek's.