tomasz86

The Windows folder can't have spaces so you don't need quotes (unless you set the variables manually to something else but it's not the case here). Microsoft themselves usually don't use quotes when pointing to %windir% / %systemroot% in their patches. Newer Windows can also use WINNT, ex. when you upgraded your system from Windows 2000 to XP, later upgraded XP to Vista, and Vista to 7, etc.

I wanted to use both double quotes and spaces as delimiters but I didn't know how to do it so I searched for a solution in the Internet but couldn't really find anything useful. Finally I've managed to figure it out by myself and I'm posting this in case someone else encounters a similar problem: FOR /F delims^=^"^ %%A IN ("abc = "1"") DO ECHO "%%A" It will display just "abc" Notice that there are two spaces before %%A.

I don't know if there are any hotfixes available but the updates are here. I haven't updated the list recently but there should be 2809289 available for it too which replaces 2792100.

It seems to be possible in Windows 2003 but not in Windows 2000. You can create multiple pagefiles though: http://support.microsoft.com/kb/237740

The Intel graphics driver will likely not work with PAE enabled AMD/ATI drivers seem to be a hit-or-miss, and NVIDIA drivers work just fine. There are some rare occasions when some applications may not work properly (ex. here) but apart from that, no problems with PAE. I've got 8 GB of RAM but actually use half of it for a RAMdisk:

I've experienced similar issues several times, usually in case of laptops. It seems that something is incompatible with the Windows 2000 installer. It's not necessarily the SATA driver, since I had exactly the same situation on an older laptop with IDE disk controller. It doesn't mean that Windows 2000 won't work on the computer. It's just the installer which has problems. One way to overcome is would be to take out the HDD, connect it to a different machine, install the system there and then move it back. Having same disk controller in both computers would make it a lot easier.

Not necessarily There are three different lines - daily, weekly and stable (details in #1). The one which you linked to is the newest daily release of UURollup-v11. The current releases are: stable - Windows2000-UURollup-v10d-x86-ENU.exe weekly - Windows2000-UURollup-v11-w20130323-x86-ENU.exe daily - Windows2000-UURollup-v11-d20130323-x86-ENU.7z You can test any of these.

I've added one more test done using a newer version of makecab. It seems to be exactly as fast as cabarc.

It was cabarc.exe 6.2.9200.16438 (from Windows 8), expand.exe 6.1.7600.16385 from Windows 7 and 7z.exe 9.20.0.0. All tests were conducted in Windows 2000. I'll try to check other versions later.

Can you enable IDE mode in BIOS?

7-Zip 7z.exe x 1\* -o"2" >NUL Time: 0:24 FOR /F "delims=" %%A IN ('DIR/B/S 1') DO 7z.exe x "%%A" -o"2" >NUL Time: 1:08

The test is using the same file base as that one. This time I just compressed the files from the "2" folder in order to see if there's any difference between makecab.exe and cabarc.exe when compressing files with LZX:21 compression. makecab.exe 5.0.2147.1 (from Windows 2000) FOR /F "delims=" %%A IN ('DIR/B/S 2') DO makecab /D CompressionType=LZX /D CompressionMemory=21 "%%A" /L 3 >NUL Time: 7:51 makecab.exe 6.1.7600.16385 (from Windows 7) FOR /F "delims=" %%A IN ('DIR/B/S 2') DO makecab /D CompressionType=LZX /D CompressionMemory=21 "%%A" /L 3 >NUL Time: 7:03 cabarc.exe 6.2.9200.16438 (from Windows 8) SETLOCAL ENABLEDELAYEDEXPANSION FOR /F "delims=" %%A IN ('DIR/B/S 2') DO ( SET File=%%~nA. SET "Ext=%%~xA" && SET File=%%~nA!Ext:~0,-1! cabarc -m lzx:21 N 3\!File!_ "%%A" >NUL ) Time: 7:05

I wanted to say that Cabarc is always faster but the difference isn't that dramatic in case of 1. and 2. On the other hand, 2. is MUCH faster than 3.

I was wondering if there's any difference in speed when extracting files using expand.exe and cabarc.exe so I've just done a simple test. I took all *.*_ files from XP SP3 (2674 files total), put them into a folder called "1" and then expanded all of them into a new folder called "2". EXPAND -R 1\* 2\ >NUL Time: 0:42 FOR /F "delims=" %%A IN ('DIR/B/S 1') DO cabarc x "%%A" 2\ >NUL Time: 0:33 FOR /F "delims=" %%A IN ('DIR/B/S 1') DO EXPAND -R "%%A" 2\ >NUL Time: 6:08 Cabarc.exe is almost 25% faster than Expand.exe when used like in 1. and 2. but if you use Expand.exe in a loop like 3. then it's time to switch to Cabarc.exe since the difference in speed is huge.

Not really You can try other tools like YUMI but I'm not sure whether it will work properly with Window 2000 source. Still, one hour seems to be a little too long even for WinSetupFromUSB unless you're using a very low quality USB stick...

It's may be different problem but just in case you may try to slipstream the original XP drivers. In order to do so you should start with a clean source again, i.e. don't add them to the source where you've already integrated my drivers as the system won't be able to choose the right one.

HFSLIP is similar to nLite in some aspects. It's better than nLite when it comes to slipstreaming of Windows updates. nLite offers other customisation which isn't available in HFSLIP. I'd suggest you go to my Download Archive and then: Go to Windows2000/UnofficialSP5/HFSLIP, download HFSLIP_ia.7z and unpack it to a folder (make sure there are no spaces in the path). Copy your Windows 2000 source to the SOURCE folder. Run the script and wait until it's finished. In the Download Archive go to Windows2000/UnofficialSP5/Drivers and download AMD 12.10 AHCI SB8xx.7z. Use nLite to integrate the driver. Use WinSetupFromUSB (the newest beta) to prepare a USB stick. Install Windows. We'll think about the other drivers after the system has been installed but from my experience I can say there might be a problem with the Atheros WiFi. The rest should work fine. PS Sorry about confusing the flags but here on MSFN it really looks like the Italian one...

Thanks for everything I actually thought that FCIV was rather slow but now I can see that it's not true, especially compared to some of the other tools tested by jaclaz which turned out to be very slow.

What language version of Windows 2000 do you use? If it's Italian then probably the only way to retain both the original system language and be able to to install the system with AHCI (SATA) enabled would be to use blackwingcat's modified AMD drivers. On the other hand, if it's an English system or you don't care for the language, then you could use my HFSLIP package to prepare a fully updated Windows 2000 source and then slipstream the XP drivers. Most of your system's language will change into English if you use an Italian source. I can probably help but first let me know which of the two ways you prefer. It would also be nice if you provided some more details about the laptop. Full technical specification would be very useful (especially the hardware ID of the SATA controller). I'd also suggest using a USB stick to install the system instead of CDs since it's much faster and rewritable. If you want to stick to CDs then how about buying just one CD-RW?

I'm not 100% sure but it seems that PARTCOPY doesn't work at all when PAE is enabled (at least in Windows 2000). Nothing happens when it's executed. No errors, just nothing. I used it in my script to create MSCF.SFX before but because of this reason I've recently switched to the split.exe recommended by submix8c since it works fine.

You seem to like "§" a lot but do you remember that it was also present in your original SPLITINF script... and the problem was that it didn't work when system locale was set to Korean and in the end I had to replace it with something else which was "}#}" so I'd like to avoid using such characters.

I was wrong. It still doesn't ECHO lines starting with ";" when EOL isn't defined I'll probably use: FOR /F delims^=^ eol^= %%A IN (1.inf) DO ECHO %%A when I want to display full lines and FOR /F tokens^=1-2^ eol^=^ delims^=^,^ %%A IN (1.inf) DO ECHO %%A,%%B when I need to specify delims, one of which is space.

Thanks for the program. It works in stock Windows 2000. I've also tested it in NT 4.0 but it doesn't work there (it generates same output regardless of the switch used).

The script doesn't work for me I've just tried it on several EXE and DLL file and the MD5 generated didn't match the real one. It's indeed slow (4 min for a 500 KB file on Athlon II X4 631). As for FCIV, that's what I'm doing now. It's downloaded automatically if not already present. I'll check the other method of creating the binary which you've suggested.

Never mind I'll let you know if I encounter any problems. By the way, is FOR /F "tokens=1,2 delims=, " %%a in ('TYPE 1.inf') do echo %%a,%%b any different from FOR /F "tokens=1,2 delims=, " %%a in ('FINDSTR "^" 1.inf') do echo %%a,%%b ?