tomasz86

Nice I'm wondering if these lines are absolutely necessary: 1. If WScript.Arguments.Count <> 2 then WScript.Quit end If 2. objInputFile.Close objOutputFile.Close The script seems to work without them too...

This is a "minified" version of the silent yanklines script which is created on the fly from commandline: ECHO>yanklines.vbs ^If WScript.Arguments.Count ^<^> 2 then ECHO>>yanklines.vbs WScript.Quit ECHO>>yanklines.vbs end ^If ECHO>>yanklines.vbs Const ForReading=1, ForWriting=2 ECHO>>yanklines.vbs Dim i,j ECHO>>yanklines.vbs Set objFSO=CreateObject("Scripting.FileSystemObject") ECHO>>yanklines.vbs Set objInputFile=objFSO.OpenTextFile(WScript.Arguments.Item(0),ForReading) ECHO>>yanklines.vbs Set objOutputFile=objFSO.OpenTextFile (WorkingDir ^& WScript.Arguments.Item(1),ForWriting,True) ECHO>>yanklines.vbs Set objDict=CreateObject("Scripting.Dictionary") ECHO>>yanklines.vbs objDict.CompareMode=1 ECHO>>yanklines.vbs j=0 ECHO>>yanklines.vbs On Error Resume Next ECHO>>yanklines.vbs While Not objInputFile.AtEndOfStream ECHO>>yanklines.vbs arrinputRecord=split(objInputFile.Readline,"vbNewLine") ECHO>>yanklines.vbs strFirstField=arrinputRecord(0) ECHO>>yanklines.vbs ^If objDict.Exists(strFirstField) then ECHO>>yanklines.vbs j=j+1 ECHO>>yanklines.vbs Else ECHO>>yanklines.vbs objDict.add strFirstField,strFirstField ECHO>>yanklines.vbs End ^If ECHO>>yanklines.vbs Wend ECHO>>yanklines.vbs colKeys=objDict.Keys ECHO>>yanklines.vbs For Each strKey in colKeys ECHO>>yanklines.vbs objOutputFile.writeline objDict.Item(strKey) ECHO>>yanklines.vbs Next ECHO>>yanklines.vbs objInputFile.Close ECHO>>yanklines.vbs objOutputFile.Close Maybe someone will fine it useful.

Use DriverPacks BASE to integrate the drivers and do it after everything is finished in nLite.

These are the newest ones: Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package MFC Security Update Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package MFC Security Update Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package MFC Security Update You will still need to install a few security updates from WU though.

One more important thing to note about the "[unattended]" problem. Make sure that your original WINNT.SIF doesn't contain this part: [Data] UnattendedInstall="Yes" because after using WINNT32.EXE it will be converted to [unattended] unused=unused therefore resulting in an unattended text part of the installation. By the way, I've just tested it. It's different When the /noreboot switch is used this screen still appears: but nothing happens after the counting has finished. It just disappears Edit: One more very important information. When the setup is started using a CD or any other external device and you haven't integrated mass storage drivers for your controller then the setup will simply not detect any drives. In case the setup is started from the disk itself you MUST integrate the mass storage drivers because otherwise loading during the text setup drivers will result in a BSOD. Also if it's Win2k and a disk larger than 137 GB then you also MUST enable the 48-bit LBA to prevent the crash.

I've found the culprit. WINNT.SIF was actually copied correctly. The problem is very different here. Having the "[unattended]" section leads to an unattended text part of the Windows setup. What I mean is that just adding [unattended] (it can be empty) to WINNT.SIF will lead to an automated text part of the installation The EULA will be skipped and the partition will be selected automatically. What's more, even settings like AutoPartition="0" under [Data] or Repartition="No" under [unattended] don't make any difference. The same thing applies to the DOS based installation. I don't know wherther it's Win2k specific or happens in XP/2003 as well. Edit: I've removed the "DOS" part from the topic's title since it's no longer relevant as we've been discussing both WINNT.EXE and WINNT32.EXE based methods of installation.

Something is broken with validation when downloading updates. On XP you can still install the WGA update (I don't remember its KB number) and download the files. Under 2000 it's impossible... BUT it's possible to download the files using a little "trick". You need to use the "confirmation links", ex. Original: http://www.microsoft.com/en-us/download/details.aspx?id=30617 (requires validation) Confirmation: http://www.microsoft.com/en-us/download/confirmation.aspx?id=30617 (no validation required) This way you can download the updates for all languages except ARA and HEB. If you check the URLs for 2732052 on the Win2k updates list you can see how they should look like for the other languages. You only need to change the ID number at the end of the URL.

To make it simple - you probably need to integrate the mass storage (SATA) drivers. You can do it on a different computer and then burn the new XP CD with the drivers integrated. Use nLite to do it. You should be able to find the drivers on the laptop manufacturer's website.

Thank you for all the information That's why (originally) I wanted to have both the I386 folder and the system installed on the same partition when the setup was started from DOS because if the I386 had been on a different one than at the end the system drive would have had a different letter than "C" assigned (and I wanted it to be "C"). I hope there won't be any problems now when WINNT32.EXE is used to prepare the partition. I don't really intend to use such a setup on a different computer (my question was asked just out of curiosity). I'm going to use this installation method on my desktop to test different things. It's the fastest installation method I've tried here. Of course when deploying the system on a different computer it might be useful to have a copy of the I386 folder there. Now I'm experiencing a different problem related to the unattended file. I still need to do some tests to be 100% sure but even though I used /unattend:WINNT.SIF the setup seems to use the default UNATTEND.TXT

It's from French http://fr.wikipedia.org/wiki/Illusionnisme#Techniques_de_prestidigitation http://www.thefreedictionary.com/prestidigitator

O|\|E Nn()0|2E 70() 7|-|E {0011e(7!()()|\| :* http://pokemontranslator.pl/

M$ EULA itself is probably illegal in most countries

BOOT.INI is of course there (my mistake for running dir/b without the /a switch which resulted in omitting the hidden files). It is a real NTLDR but is copying the whole I386 folder required? I'm using the "/makelocalsource" switch which is supposed to: By the way, I've got a problem with the "/noreboot" switch. Even though I added it to the command, it still wanted to restart the machine after copying the files

From my experience nVIDIA is much more friendly than ATI/AMD. If you don't need a gaming card then even a used 10$ nVIDIA card should be enough for other graphic activities like playing video files, etc.

While testing installation from DOS (click) I have found out that there are two files in Update Rollup 2 which don't follow the standard 8.3 format. Normally they're located inside one of the CABs but HFSLIP doesn't add them there but rather slipstreams them separately. Because of that they can't be copied when Windows setup is being run from DOS I've also found another problem. The unofficial KB973904-v3 was created in order to make slipstreaming possible because the original update added new Wordpad files which weren't originally present in the system. The problem was "fixed" by adding a modified wordpad.inf where new entries related with the newly added files were added. Now the problem is that it doesn't work in a HDD based system installation. I hadn't experienced any problems before when using a bootable USB but when installing the system from HDD the installer just cannot find the files! Fortunately, you can still search for them manually. I'm going to try modifying the wordpad.inf file differently and see whether it makes any difference. If it doesn't help then editing the layout.inf may be inevitable. @acus Hmm, I've been trying to get the new wintrust.dll work properly during slipstreaming but no success yet. Did it work for you after "patching" the sfc.dll and removing the "_x" in the lines related with layout.inf?

I've found out what was blocking the WINNT32.EXE. I had "HKLM\SYSTEM\CurrentControlSet\Control\ProductOptions" denied from access (in order to install Avast in a Server system ) and WINNT32.EXE couldn't determine what version of Windows 2000 it was. Now I should be able to just use it directly to set up a bootable HDD partition, right? I hope this will work: winnt32 /tempdrive:G /unattend:WINNT.SIF /syspart:G /makelocalsource /noreboot Edit: I'm still wondering what is the problem with mbrfix.exe. The other RAID partition connected to the same controller is accessible, only this one (G:) not. By the way, just a kind of related question. After running the command mentioned above the following structure has been created on G: $LDR$ $WIN_NT$.~BT $WIN_NT$.~LS BOOT.INI ntdetect.com ntldr txtsetup.sif Could this be copied to and used on another partition directly after formatting it under Windows NT with format.com? Do you still need to set up the MBR separately? Edit Fixed the structure (added BOOT.INI).

Actually, if I'm not mistaken, the original WMP9 link has been dead for a long time (months if not years ).

@Kurt_Aust Your link to WMP9 from the first post is dead. Maybe you could update it to the one listed here: http://www.windows2000.tk/updates/index.html#kb316992 It's the direct URL for the same file (the MD5 matches yours).

Thanks a lot for this information!!! You are 100% right. The version from Kurt_Aust is newer than the one available to download from MajorGeeks or Softpedia. Of course it's better to use that one instead of the older ones. I'll need to update the information on my website. The result would be very different. USP5.1 installs files which come from hundreds of HBRs (hotfixes by request). Those files are not included in any official M$ update (rollup). That's one of the reasons why it's better to use it instead of the official packages If WMP9 works then I think it would be better to focus on other things at the moment as I can't reproduce the error on my system so it's very difficult to trace it Could you list all of your hardware in details?. We can try to integrate the drivers using my script but it must be exactly clear which files are required to integrate. No but having the file in the system may be useful later. That's why it's located in HFEXPERT\WIN\system32 which means that it will be copied to %systemroot%\system32.

Trying to use WINNT32.EXE was the first thing I did but it doesn't work here. I don't know the reason but trying to run it (with any switch) results in: I've got a problem when trying to use mbrfix.exe. I tried to change the bootsector using: mbrfix /drive 0 /partition 1 fixbootsector win98 and while everything seems to work OK initially, after reboot it's still the NT 5.x MBR. Moreover, after creating a primary partition using Device Manager and formatting it to FAT32 when trying to use: mbrfix volumeinformation g: I get this: Strangely enough the command works for the other drives but fails on this one.

I need to do some extensive testing connected with slipstreaming on a real hardware and I've become sick and tired of using a USB flash disk each time to install the system simply because it's just too slow and requires preparing the drive again and again each time when the source has been altered. The installation itself is fast but preparing the drive (=copying 6000 of system files on it) takes too much time. I know that there are ways to install using the ISO image but I wanted to try installing the system directly from HDD without using any other devices.It had been a long time since I used DOS to start Windows setup so I had to search for and read some information about it, try it, fix errors, try again, fix errors again, etc. This is what I've managed to accomplish so far: I created a 4GB FAT32 partition on a separate HDD. Using HP USB Disk Storage Format Tool and MS-DOS files I prepared a DOS bootable Flash Drive with the following files: COMMAND.COM FORMAT.COM IO.SYS MSDOS.SYS I booted from it and used FORMAT.COM to format the 4GB FAT32 partition (D:) in order to make it bootable: format d: /q /s After booting back to Windows I copied the I386 folder to the 4GB partition. I also added SMARTDRV.EXE, HIMEM.SYS and CONFIG.SYS with the appropriate settings: device=HIMEM.SYS /testmem:off I created AUTOEXEC.BAT with the following lines: SMARTDRV.EXE C:\I386\WINNT.EXE /S:C:\I386 /U:C:\I386\WINNT.SIF The WINNT.SIF was of course prepared in advance. In the end the partition contained the following files and folders: I386 SMARTDRV.EXE COMMAND.COM AUTOEXEC.BAT CONFIG.SYS HIMEM.SYS IO.SYS MSDOS.SYS I booted to the partition and the system setup was started automatically. Just in case I disabled / disconnected all other HDDs. When selecting the partition (I wanted to install the system on the same 4GB one) I could choose whether to convert it to NTFS or not. The setup continued normally. After everything finished I could remove the I386 folder as it was not required any more. That's basically everything I did. In the beginning it didn't work so smoothly but after trial & error testing it seems to work fine. There are some things to be careful about like filenames which don't follow the 8.3 name format as the DOS based part of the installer won't be able to copy them. Overall the installation itself is pretty fast and you don't need to use any other devices after the HDD is made bootable (step 3). What I'd like to ask is whether this method could be improved. I'd especially like to make a bootable DOS partition without having to use a USB flash disk (step 2 & 3). In other words, is there any simple way to use the DOS' format.com under Windows or maybe are there any alternative tools to use instead of it?

Thanks a lot. I've found it. I'm weak at hex editing

Have you actually found any issues when your kernel is used with any of the two packages...? Both of them install files from the official updates and hotfixes only. Edit: I can see that you've edited your post Please let us know if you do test the packages with your kernel and find any problems.

There is a simple way to update your system if you're lazy. It won't be fully updated but maybe around ~85%. 1. Install Unofficial SP 5.1 (USP5.1) 2. Install Update Rollup 2 (UR2) 3. Install the IE6 update mentioned above. Then you can install the BlackWingCat's kernel.

Okay back with one dumb question? Where can I find those two files^... could you link them please? IE6 you can download directly from M$: http://download.microsoft.com/download/ie6sp1/finrel/6_sp1/W98NT42KMeXP/EN-US/ie6setup.exe and the other update you can find on the Windows 2000 Updates list: http://www.windows2000.tk/updates/ However, it seems that your system is not fully updated. I'd recommend installing at least all available official updates before applying any unofficial patches.