Content Type
Profiles
Forums
Events
Everything posted by fdv
-
Post your ini. You removed no components? Just added things, right? Do you have a virtual PC program you can use to troubleshoot this problem? That would help. Microsoft's VPC 2004 is free now; I suggest starting with that.
-
Hey, man! (waves) Open Regedit Go to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer You will see values for IncludeSubFolders SearchHidden SearchSlowFiles SearchSystemDirs Set them all to 1. Then either restart Explorer or reboot the computer. (One hopes the reg settings will stay)
-
CDROM boots Windows loads LAYOUT LAYOUT copies files from the CDROM to your hard drive (usually its bootable partition, or C:) Setup restarts and TXTSETUP copies files from the bootable partition (probably C:) to their final places. So, the bottom line answer is, when booting from CD, setup files are located in C:\$WIN_NT$.~BT and C:\$WIN_NT$.~LS
-
This is a weird one. The only thing I can think of at this point is to eliminate XP's looking for the tag file. Try editing TXTSETUP like this: [Version] signature="$Windows NT$" ClassGUID={00000000-0000-0000-0000-000000000000} [SourceDisksNames] _x = %cdname%,,,"" _1 = %cdname%,,,"" _2 = %cdname%,,,"" _3 = %cdname%,,,"" _4 = %cdname%,,,"" _5 = %cdname%,,,"" _6 = %cdname%,,,"" 1_ = %cdname%,,,"" 2_ = %cdname%,,,"" 3_ = %cdname%,,,"" 4_ = %cdname%,,,"" 5_ = %cdname%,,,"" 6_ = %cdname%,,,"" [SourceDisksNames.x86] 1 = "Windows XP Professional CD-ROM",,,\i386 2 = "%cd2name%",,,\cmpnents\tabletpc\i386 3 = "%cd2name%",,,\cmpnents\mediactr\i386 4 = "%cd2name%",,,\cmpnents\netfx\i386 _1 = %bootname1%,,,"" _2 = %bootname2%,,,"" _3 = %bootname3%,,,"" _4 = %bootname4%,,,"" _5 = %bootname5%,,,"" _6 = %bootname6%,,,"" 1_ = %bootname1%,,,"" 2_ = %bootname2%,,,"" 3_ = %bootname3%,,,"" 4_ = %bootname4%,,,"" 5_ = %bootname5%,,,"" 6_ = %bootname6%,,,"" 7 = %cdname%,,,\i386\lang 8 = %cdname%,,,\i386\lang 9 = %cdname%,,,\i386\lang 10 = %cdname%,,,\i386\lang 11 = %cdname%,,,\i386 12 = %cdname%,,,\i386 13 = %cdname%,,,\i386 14 = %cdname%,,,\i386 15 = %cdname%,,,\i386 107 = %cdname%,,,\i386\lang 1984 = %cdname%,,,"\i386\NLDRV\001" 1985 = %cdname%,,,"\i386\NLDRV\002" 1986 = %cdname%,,,"\i386\NLDRV\003" IMPORTANT NOTE! Windows 2000 and XP both still look for the CD tag files in many of their driver INF files. So if you get the insert SP2 CD error further along in the setup process, you have to tackle the INF files in the devices to install section of SYSSETUP. I've seen (and solved) this error dozens of times, but it's strange that you guys keep seeing it. It might be a driver INF after all.
-
You might try a local edit using REGEDT32 (runas, etc). I never had to do this so that's a stab in the dark. This one is guaranteed, though: on future installs, add this line to HIVEDEF.INF: HKCU,"Software\Policies\Microsoft\Security","CheckAdminSettings",0x00010001,02,00,00,00
-
Of course, K's quite right, this would be the first thing to check! (If that doesn't work, I'll put your TXTSETUP on my server, changed slightly)
-
Although there is a generic SATA driver, I would agree -- use the Driverpack. This is how you integrate a driver manually in Win2k (it's the same for XP). In this case you would use UNIATA for XP. More trouble than it's worth to do it by hand IMO.
-
Sorry sorry sorry! Under [sourceDisksNames.x86], you will see 100 = %spcdname%,%spcdtagfilei%,,\i386,1 Simply change this line to 100 = %cdname%,%cdtagfilei%,,\i386 We want to get rid of the spcdname variable. In my earlier post, what you would have done is replace every single = 100,, with = 1,, (don't forget the commas). The above change is simply one edit and is therefore easier.
-
I've fixed these by hand for some time. Everyone in the thread, reply by posting your TXTSETUP files, and I'll fix them.
-
Stop. Everyone... just stop. Download his TXTSETUP file. Then re-read my post. HIS FILE IS CORRUPTED. Without the [HardwareIdsDatabase] header ANYWHERE in the file, there will be no devices that will be detected by XP at installation time. So he tries it with nLite automatically, and it still doesn't work. Time to tell him to post his TXTSETUP file after nLite has integrated the drivers. It's called troubleshooting, and you guys do a real disservice to posters when you make recommendations without analyzing the problem they're having by reading the file(s) they post. Benetnach, post the TXTSETUP file after you tried nLite's automatic driver integration, and let's see what's happening.
-
There is a MASSIVE error in this file. Search for zlogic.cyz = 1,,,,,,,,3,3 The next line is 1394\609E&10483 = "sbp2port" !! There needs to be a [HardwareIdsDatabase] header at the top of this section. You also have to put the Hardware ID data in here from your txtsetup.oem driver file so that your SATA chipset is detected. If you did not edit this file at all, then this might be a bug in nLite. Do a text search for "HardwareIdsDatabase" and it doesn't appear in the file! Something's seriously wrong. These TXTSETUP files in XP are a total mess, and about 50% of the file can be deleted -- entire sections. Although I won't be able to get to it until after the weekend, if you want to send me or post your pre-nLite TXTSETUP, I can clean it up so that it's still nLite compatable but WAY easier to troubleshoot.
-
Get on a different machine and assemble a PE. Use it to copy data from the drive. If you don't have an XP license, use the Microsoft trial version of Windows Server 2003. I recommend Ultimate Boot CD 4 Win as your PE creator. Trail of 2003. Ultimate Boot CD for Windows. There are also bootable Linux distros that could accomplish this as well... all you're looking to do is mine some data and copy what you can.
-
This is, I am sure, a naive question. I literally don't know what to search for in Google to get an answer to this... I have an old dual processor Pentium II (that's 2!) with each proc running at 350MHz. I have a RAID 1 card in it with 2 SATA drives, and a gigabit ethernet card. 192MB memory, and a VERY bare bones Windows 2000. It works fine as a plain file server and nothing else (it literally runs no programs, just the OS). But I have a nagging suspicion that I am holding the system back because of the processors, or the bus pseed, or the memory... but I have no idea. I mean, the drives are on a separate controller, and it has GB Ethernet, so the fact that it's old hardware shouldn't make a difference. Right? Someone help an old-schooler out
-
No prob. [Version] Signature = "$Windows NT$" [DefaultInstall] AddReg = addreg DelReg = delreg [addreg] ; ; Reassign from CLSID_HTMLDocument to CLSID_IImageDecodeFilter ; HKCR,"pjpegfile\CLSID",,,"{607fd4e8-0a03-11d1-ab1d-00c04fc9b304}" HKCR,"xbmfile\CLSID",,,"{607fd4e8-0a03-11d1-ab1d-00c04fc9b304}" HKCR,"jpegfile\CLSID",,,"{607fd4e8-0a03-11d1-ab1d-00c04fc9b304}" HKCR,"pngfile\CLSID",,,"{607fd4e8-0a03-11d1-ab1d-00c04fc9b304}" HKCR,"giffile\CLSID",,,"{607fd4e8-0a03-11d1-ab1d-00c04fc9b304}" [delreg] ; ; fix graphic extensions so they are no longer IE ; HKCR,"pjpegfile\shell\open" HKCR,"pjpegfile\DefaultIcon" HKCR,"xbmfile\shell\open" HKCR,"xbmfile\DefaultIcon" HKCR,"jpegfile\shell\open" HKCR,"jpegfile\DefaultIcon" HKCR,"pngfile\shell\open" HKCR,"pngfile\DefaultIcon" HKCR,"giffile\shell\open" HKCR,"giffile\DefaultIcon" [Strings] You want Windows 2000 settings to be in place when you install the OS, have a look at IE.INF in my fileset. It's got all sorts of goodies and can show you all sorts of things via example.
-
I think in general you'll find that a OEM driver is usually preferable to a built-in Windows driver. You cannot depend on MS doing the right thing in this department. For example, compare low-level drivers in 2000 with XP such as fastfat.sys or pcmcia.sys. Why won't MS update the 2000 drivers by issuing a rollup for 2000 that has the XP drivers? They won't, of course. Do you have a link to the Intel generic USB driver? I'm interested in checking that out.
-
[MAC]Should I use another's configuration or make my own?
fdv replied to puffenstuff's topic in nLite
For your sanity, use nLite. Say you try to clone someone else's method for slimming down XP, and then discover you're missing something that games or CAD needs. With nLite, it's been in use so long by so many people that you're getting a known quantity. nLite comes with support in this forum and you have the benefit of many fellow users who might not be able to help you work out the kinks in someone else's non-nLite method. -
If you keep swapping hardware out, the WPA data file won't help. XP sees it as a new computer after a few hardware changes. You could do like I did (but with Office XP) and call them to "reset the key" (which they told me they could do TWICE on TWO separate phone calls) only to have them tell you that that's impossible on the third call. (It felt really good to be treated that way after I'd bought a few thousand dollars' worth of licenses and a VLK and they said it was OK to install one retail copy over and over during deployment, since I had all of the licenses and was 100% legal... and after the fourth install, the key went bad.) Anyway, your limitation here is not with nLite or any action you can take. The best thing to do, if you can, is to go to e-bay and try to upgrade XP by buying a copy of Windows 2000. You'll have a faster OS, a cleaner interface, and several other enhancements like a lack of compatibility with IE7.
-
As far as I can see though that creates a dot Z file, it doesn't makecab FILE.SYS >> FILE.SY_
-
This is cheating, but it's one way to fix the problem. Open TXTSETUP.SIF Edit, Replace ever single = 2,, with = 1,, (don't forget the commas). Save. Setup will never look for a SP2 descriptor. Open LAYOUT.INF and delete the _x in two lines (just the _x, leave the commas) layout.inf = 1,,384649,,,,_x,20,0,0,,1,20 txtsetup.sif = 1,,449813,,,,_x,,3 Save. Setup will not check layout or txtsetup against the file sizes listed in those lines (_x forces a filesize check) I know this doesn't answer from an nLite standpoint, but it will fix the problem
-
He means CLSIDs in general. You can create them in Visual C++ for your apps, and MS's software generated them randomly. In the Windows OS, yes, they have a consistent meaning, but way back when, when Windows 2000 was created, all of the OS component CLSIDs started life this way -- as randomly generated numbers when Microsoft was compiling the libraries.
-
I know double posting is kind of lame, but this is so short I hope no one minds. Although this won't makecab everything in a folder, it will add Compress as a context menu option to dll and exe files, and expand as an option to compressed exe, dll, inf, and sys. You can select as many DLL and EXE files as you want and left click and you will see "Compress" as an option. Select it, and every one of your selected files will be compressed. [Version] signature="$Windows NT$" [DefaultInstall] AddReg = addreg [addreg] HKCR,"exefile\Shell\Compress\command",,,"%11%\makecab.exe ""%1""" HKCR,"dllfile\Shell\Compress\command",,,"%11%\makecab.exe ""%1""" HKCR,".dl_\Shell\expand\command",,,"%11%\expand.exe -r ""%1""" HKCR,".in_\Shell\expand\command",,,"%11%\expand.exe -r ""%1""" HKCR,".ex_\Shell\expand\command",,,"%11%\expand.exe -r ""%1""" HKCR,".sy_\Shell\expand\command",,,"%11%\expand.exe -r ""%1"""
-
Add Compress as a context menu option to .DLL and .EXE files A bump because I figured out a REALLY simple way to work with files. Although this won't makecab everything in a folder, it will add Compress as a context menu option to dll and exe files. You can select several of both kinds and it will makecab them all: select as many DLL and EXE files as you want and left click and you will see "Compress" as an option. Select it, and every one of your selected files will be compressed. [Version] signature="$Windows NT$" [DefaultInstall] AddReg = addreg [addreg] HKCR,"exefile\Shell\Compress\command",,,"%11%\makecab.exe ""%1""" HKCR,"dllfile\Shell\Compress\command",,,"%11%\makecab.exe ""%1""" HKCR,".dl_\Shell\expand\command",,,"%11%\expand.exe -r ""%1""" HKCR,".in_\Shell\expand\command",,,"%11%\expand.exe -r ""%1""" HKCR,".ex_\Shell\expand\command",,,"%11%\expand.exe -r ""%1""" HKCR,".sy_\Shell\expand\command",,,"%11%\expand.exe -r ""%1"""
-
Thanks TC, I remember now. In the first betas it was CHANGE then it became SWAP and then HFNEWER and HFCHANGE before becoming HFFIX which got changed to REPLACEFIXHFNEWERCHANGE. Wela, yes, I recommend those two files too. Anyone else try and see a speed increase? What would happen if I combined DRIVER.CAB files, would that even work? Taking out kernel files of course. What about URL and WININET? I'm'a try these right now I think. BTW, Schiller is awesome. Just wanted to add that.
-
I am running a dual core and I run VMWare 6. I have been experimenting with various settings in Windows 2000 and I'm pretty used to the time setup takes. It's not slow, but I had a pretty good grasp on it. I put the following files from Server 2003 into HFREPLACE/i386: aic78u2.sys aic78xx.sys atapi.sys cdfs.sys dmboot.sys fastfat.sys intelide.sys ntfs.sys ntfsdrv.dll pci.sys pciide.sys pciidex.sys ultra.sys untfs.dll Now I might be wrong, but I could swear my setup time was reduced by quite a bit. Now, some of these files wouldn't even get used by the OS in VMWare, I recognize that... aic78xx.sys for example, because the OS doesn't detect that SCSI card since it's not on my system and not emulated in VMWare. But files like pci, cdfs, atapi, and ntfs for example I know are used. You guys might want to try playing around with low-level drivers too to see your results.