tomasz86

This is an image created after using "format /q" in Windows 2000. I used a virtual floppy drive and I'm not sure if everything was done correctly but please check it. 2KIMA.7z

@Molecule I don't remember myself writing about XP SP3 USB related files in 2K... Those files are incompatible with 2K and can't be used as they are. I did mention somewhere that it might be possible to use XP Beta ("Whistler") files but I haven't tried them yet. It's pretty complicated because in order to do that ALL of the original USB related files would have to be replaced. I don't really use USB based backups so I don't know too much about it and won't probably be able to help you with this problem. As for WinSetupFromUSB, in order to use it in Win2k you must download the previous beta version (not the newest one), and then open "Advanced Options" and enable displaying all drives there. After doing so you'll be able to select your USB device (use keyboard arrows to switch between them). You also should format the device using the system Disk Management (or just "format" from command line) instead of using the tools from WinSetupFromUSB. Have you got the drivers for ICH10 integrated in your source? You should use the ones from BlackWingCat (http://blog.livedoor.jp/blackwingcat/archives/813816.html). nLite should be able to integrate them.

This is exactly what I mean. When the unofficial kernel is used then you should be able to just use the official drivers for XP but without it you must use the ones modified by BlackWingCat. If your system were in English then I'd just recommend installing the kernel but as it's in German there's no other way than just trying to install all of the BlackWingCat's drivers one by one until you find a working one. In fact, you can "forcefully" install the unofficial kernel in a German system but then some parts of the system will change into English.

First of all, let's focus on the desktop: Download and install the latest daily version of UURollup. You can find it in the Archive (navigate to "Windows2000\UnofficialUpdatesRollup\Daily"). Download and unpack it, go to "update" and run "update.exe". Download the official AMD drivers from here. Try to install them using the official installer. If it doesn't work then unpack the installer and try to install them using the Device Manager and pointing to "Packages\Drivers\Display\XP_INF" in the unpacked installer folder. Can you see the whole 8 GB of RAM in the system? If not then open "%systemdrive%\boot.ini" (it's hidden by default and may be set to read-only) and change the line (it will be a little bit different depending on your setup): multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Advanced Server" /FASTDETECT to multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Advanced Server" /PAE /FASTDETECT I'd also recommend adding /3GB so the final line should say: multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Advanced Server" /PAE /3GB /FASTDETECT Reboot and check the result. In case the system doesn't start press F8 and choose "VGA mode". Report the results. Now, as for the laptops, there may be a problem with installation and it may be necessary to use some tricks. First please: Run Speccy on each of them but this time don't do any screen shots but rather click on "File" and choose "Save Snapshot". After that upload the two snapshots so that I can download and check them directly. Have you got access to the disks in the two laptops? What I mean is - are you able to easily take them out and connect to your desktop? I'm asking because sometimes it's pretty complicated depending on the notebook model.

@desertofunknown Like bphlpt has already written, I don't think that this project belongs to SourceForge simple because almost all files included in it come from M$ being either the original ones or modified versions. Therefore it's not open source. I have just uploaded a new daily version of UURollup-v11 (if it's not there yet then check again one hour later). All files have been updated to the newest available versions and I've also added several files from IE6 SP3 (they're installed only if IE6 is present in the system). The wintrust.dll problem still persists and there's also another issue with slipstreaming so at the moment this version can be only installed manually. Also starting from this version UURollup now officially requires Update Rollup 2 to be present in the system before installation.

You need to be precise, that's true but for me the cascading menus are much faster as you can see everything at once and don't need to scroll anything. You also don't need to click in order to open each of the folders - just move your mouse.

Frankly speaking, I don't really know how to solve this problem. The one thing which I can say for sure is that you cannot use the official drivers from AMD because they require the unofficial kernel to work. Is your system German? How about trying out the older versions of the drivers? At the moment I'm not using an ATI/AMD graphic card but before I had some success with the 9.x drivers (you can find them on the BlackWingCat's blog).

I hate this and you don't give us an option to use the original Vista/7 style This is actually a big advantage of Classic Shell over the other alternatives which usually provide only a Vista/7 style Start Menu

@user8342 You must use the BlackWingCat's drivers (links in the first post), not the official ones.

Even if you don't know too much about HFSLIP / nLite it shouldn't be very difficult. These are the steps you need to do: Download "HFSLIP_ia.7z" from my website and unpack it to a location without spaces, ex. "C:\HFSLIP_ia". Inside "C:\HFSLIP_ia" create a folder called "SOURCE" ("C:\HFSLIP_ia\SOURCE") and copy your Windows 2000 source files (I386, etc.) there. Run the script ("hfslip-1.7.10_beta_J_v10.cmd") using the default settings and wait until it's finished. A new folder called "SOURCESS" with the updated source will be created. This step MUST be done under Windows NT 5.x (2000/XP/2003). Download "ati1208raid2k.cab" and unpack it anywhere. Run nLite, choose "C:\HFSLIP_ia\SOURCESS" as source and integrate the driver (make sure that textmode integration is selected) from "ati1208raid2k\SB8xx". Create a new ISO image with nLite, burn it on a CD (or prepare a bootable USB stick or a HDD based installation, etc.) and install the system.

I forgot to mention that you also need to copy your Windows 2000 source files into the SOURCE folder before running the script The files to integrate are already present in the other folders, aren't they?

After you've downloaded and unpacked the archive you can just run the script and wait until it has finished. This may take up to 30-40 minutes on a slower machine (from my experience disk speed is the most important). The updated source will be located in an automatically created SOURCESS folder. Is the screen shot from your laptop? You will probably need one of the BlackWingCat's drivers. Download ati1208raid2k.cab, unpack it and use files from the SB8xx folder. You can just use nLite to add this driver to your source (the updated one from SOURCESS).

@Win98 Could you give more details about your desktop? At the moment it's impossible to tell what kind of motherboard is used there. If you don't know it exactly then you can just run an application like Speccy and upload the report from it. As for the fully updated source, please check this post for details.

I always do full format on a newly bought disks as it's the most basic way to check if there are any problems (in fact, some time ago I had an error when formatting a new HDD and in the end it turned out to be defect). For recovering data you can try DMDE although be careful as it's not really for beginners. This program saved my data a few years ago, and it's free for personal use.

@desertofunknown Hmm, what do you mean exactly by using SVN? @fdv This is the exact error: and I think that these are the catalogs which cannot be installed: There are probably two easy ways to overcome it: Remove the catalogs from syssetup.inf so that setup will be able to continue with the current wintrust.dll. SFC must be disabled too. Use an official version of wintrust.dll in the first part of the setup and then replace it with the current one during T-13. This method can be implemented in a service pack but cannot in case of a rollup slipstreamed with HFSLIP. Don't you have to disable SFC when doing this too?

You still need to edit the SETUPREG.HIV though. The HIVE*.INF files are indeed executed during text setup but it's done at the very end of it while you need to select your disk / partition much earlier. It's that moment when the 48-bit LBA support must be enabled and SETUPREG.HIV is responsible for it. You should also remember that SETUPREG.HIV is different for every edition of Win2k (Professional, Server, etc.) and different for every language version too so don't try to switch them.

It should be available now. Yes, you should use a clean source. It can have any service pack (or no service pack) integrated but nothing else. Unfortunately still a long way to go

The above INF won't work The whole thing is that you need to add the changes to SETUPREG.HIV in order to make it work in the text setup. You still need the above setting later but the HDD must be properly detected in the text setup first. The SETUPREG.HIV files for each edition of Win2k which are included in USP5.1 have this setting already added.

Technically speaking there's no difference between Windows 2000 Advanced Server and other editions when it comes to installation. First of all, I'd suggest preparing a fully updated source. If you check my archive and go to "USP52" then you'll find a file called "HFSLIP_ia.7z" (if it's unavailable now then try looking for it a few hours later). Download and unpack it to a location without spaces, ex. "C:\HFSLIP_ia". After that copy your source to "SOURCE" (you basically need the I386 folder and the files "CDROM_IA.5", "CDROM_NT.5" & "CDROMSP4.TST" (the last one only if SP4 is integrated). After that just run "hfslip-1.7.10_beta_J_v10.cmd". You will end up with a fully updated source (the SOURCESS folder) and an ISO ready to be burned. Remember that HFSLIP should be run under NT 5.x (2K/XP/2K3) only. You should integrate proper SATA drivers for your motherboard. Switching to IDE mode doesn't always work. You can use nLite to do it (as long as you're going to use the system for private purpose only) or you can use my script which automatically adds drivers to DRIVER.CAB. If you're interested I can try to upload it today or tomorrow (but keep in mind that it's still a beta version).

As always, when installing Win2k on a newer hardware it's recommended to prepare a fully updated source (at least all official updates should be slipstreamed). Even if the media comes with SP4 integrated it is still very old (SP4 was released in 2003...). With the new versions of BWC kernel / UURollup & PAE enabled you can use up to 8 GB of RAM under Win2k Pro. Lastly, instead of switching to IDE mode in BIOS I would just recommend integrating proper SATA drivers.

Changing "ErrorControl" to "0" fixed the problem. This is the current version: [AddReg] HKLM,"SYSTEM\CurrentControlSet\Services\dsigning","Type",0x10001,0x10 HKLM,"SYSTEM\CurrentControlSet\Services\dsigning","Start",0x10001,0x2 HKLM,"SYSTEM\CurrentControlSet\Services\dsigning","ErrorControl",0x10001,0x0 HKLM,"SYSTEM\CurrentControlSet\Services\dsigning","ImagePath",0x20000,"cmd /c start cmd /c ""(echo \registry\machine\software\microsoft\driver signing[2]& echo policy=reg_binary 0x00000001 00)>\dsigning.txt& regini \dsigning.txt& del \dsigning.txt& for /f ""tokens=3"" %%i in ('reg query HKLM\SYSTEM\Setup /v SystemSetupInProgress ^| findstr/i ""systemsetupinprogress""') do if ""%%i""==""0x0"" for %%i in (CurrentControlSet\Services\dsigning CurrentControlSet\Enum\Root\LEGACY_DSIGNING Setup\AllowStart\dsigning) do reg delete HKLM\SYSTEM\%%i /f""" HKLM,"SYSTEM\CurrentControlSet\Services\dsigning","ObjectName",,"LocalSystem" HKLM,"SYSTEM\Setup\AllowStart\dsigning",,0x10 I've added this: for /f "tokens=3" %%i in ('reg query HKLM\SYSTEM\Setup /v SystemSetupInProgress ^| findstr/i "systemsetupinprogress"') do ( if "%%i"=="0x0" ( for %%i in (CurrentControlSet\Services\dsigning CurrentControlSet\Enum\Root\LEGACY_DSIGNING Setup\AllowStart\dsigning) do reg delete HKLM\SYSTEM\%%i /f ) ) The script checks whether it's being run during the Windows setup and the service won't be removed if the result is positive. It will be removed on the first logon after setting the permissions once again. There's just one more very minor issue though. The "dsigning" service is still visible in "services.msc" until the system is restarted. After that it disappears. Edit: By the way, this is a very detailed "regini.exe" documentation I've managed to find: http://www.tburke.net/info/reskittools/topics/regini.htm (check regini.rtf at the bottom)

It is visible in Windows 7:

I've found the culprit. The permissions are reset as soon as the drivers installation begin. Even though the service sets them to read only they're still somehow reset later. This doesn't happen when you deny access to them manually. I'm talking about this moment: What's important is that the Policy settings are still "00"! The problem is that they are changed again to 01 again later because the read only permissions are no longer valid. I did a test and didn't remove the "dsigning" service so it ran twice - in the beginning of the GUI setup and during the first system start up too. It set the permissions again and I was able to install an unsigned driver without warnings. Now there's an issue with the service because it always stops with an error and, while it was invisible during the GUI setup, the error window pops up during the first system booting

Thank you very much for help. Actually this is everything what's required: hivesft.inf [AddReg] HKLM,"SYSTEM\CurrentControlSet\Services\dsigning","Type",0x10001,0x10 HKLM,"SYSTEM\CurrentControlSet\Services\dsigning","Start",0x10001,0x2 HKLM,"SYSTEM\CurrentControlSet\Services\dsigning","ErrorControl",0x10001,0x1 HKLM,"SYSTEM\CurrentControlSet\Services\dsigning","ImagePath",0x20000,"cmd /c start cmd /c ""(echo \registry\machine\software\microsoft\driver signing[2]& echo policy=reg_binary 0x00000001 00)>\dsigning.txt& regini \dsigning.txt& del \dsigning.txt& for %%i in (HKLM\SYSTEM\CurrentControlSet\Services\dsigning HKLM\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_DSIGNING HKLM\SYSTEM\Setup\AllowStart\dsigning) do reg delete %%i /f""" HKLM,"SYSTEM\CurrentControlSet\Services\dsigning","ObjectName",,"LocalSystem" HKLM,"SYSTEM\Setup\AllowStart\dsigning",,0x10 The other entries (Enum, etc.) are unnecessary. I've just tested it in 2K & XP. I'll try to check what the problem with driver signing in a running system is about. Edit: Fixed the script. The Enum entries are automatically created when the service is started so even though it's unnecessary to create them manually, they still have to be deleted later. The HKLM\SYSTEM\Setup\AllowStart\dsigning key also can be removed.

This is very interesting. It shall be possible to avoid using SRVANY.EXE at all I'd like not to rely on SC.EXE because it's not available in 2K. That's why I'm trying to remove the service from the registry using REG.EXE which is available by default in XP/2003 and also in 2K's SUPPORT.CAB. This may be necessary to suppress driver signing in the running system: hivedef.inf [AddReg] HKCU,"SOFTWARE\Policies\Microsoft\Windows NT\Driver Signing","BehaviorOnFailedVerify",0x00010001,0 Edit: Actually NET STOP works too: cmd.exe /c ""(ECHO \registry\machine\software\microsoft\driver signing[2]& ECHO Policy=REG_BINARY 0x00000001 00)>\dsigning.txt& REGINI.EXE \dsigning.txt& DEL \dsigning.txt& NET STOP dsigning"" so it is possible to stop the service but not possible to remove it at once. Edit 2: But it seems that there's no need to use NET STOP in case of a cmd.exe service because it's always terminated automatically.