Nazgul

Off that list only NASM is a usable decompiler. HelpDeco is a chm helpfile decompiler and the rest are Java decompilers.

@bombtrack I've downloaded your files and will take a look at them today.

LispWarez, could you post your dosnet.inf file and it's location within the Windows source? I already made some changes in my code to support 64-bit Windows, but I can't verify it, because I don't have a 64-bit Windows CD. With your info I can verify it and will post an updated version.

private bool VerifySource() { if(Directory.Exists(SourceText.Text)) { if(File.Exists(SourceText.Text + @"\I386\dosnet.inf")) { return true; } else { ErrorLabel.Text="The specified Source folder does not contain a DOSNET.INF file!"; CreateButton.Enabled = false; ErrorLabel.Visible = true; return false; } } return false; }This is the only piece of code that triggers that error. It first checks if the specified directory existst and if it does, if it contains a dosnet.inf in a subdirectory called I386. I can't figure out what could be causing your problem.

I'm unable te reproduce your problem. Are you sure you're pointing at the root of your Windows folder and not to the I386 folder?

It's a known issue with the current version of DriverPack Base. You can read about it here and BTS posted a manual fix for it here.

@fifogigo: Did you restart the program between those tries, or did you do them after each other?

A new Non-Critical XP SP2 Update: KB896344 You cannot transfer files and settings from a computer that is running a 32-bit edition of Windows XP to a computer that is running Windows XP Professional x64 Edition. Download -› 1299 KB (April 14, 2005) Switches: KB896344.exe /q /n /z

RyanVM didn't include support for nLite, but nLite included support for RyanVM's pack. So you'd have to ask nuhi to make it possible to include the DriverPacks.

I created my tool to be used, so why should I mind.

I don't use it, but seeing the posted files in this topic reminded me of a topic I recently read.

Did you call RUN_ME.cmd from another directory or from the directory where the files where located. I've seen this issue before when I call it from a different location. (for example D:\UACD\RUN_ME.cmd while the current working directory is D:\DriverPacks)

<{POST_SNAPBACK}> I don't see anywhere in the guide where it has that option stated wrong. Though I'd be glad if you pointed it out. <{POST_SNAPBACK}> I apologize. It thought it was in the wrong in the main MSFN guide, but it was at b0r3d.msfnhosting.com.

There are a couple of sections in dosnet.inf which are interesting for us. The first being Directories This section contains a sort of lookup table which is referenced in the rest of the file. I split these lines at the = and trim the (possible) spaces from the beginnings and the ends. I then store them in a so called hashtable for later reference. The next sections which are interesting are the FloppyFiles.? sections, where ? is a number. (So not the FloppyFiles.x one) You can just ignore the empty lines. The none empty lines are made up of the folowing syntax folder,source[,destination].If we look at the d1,disk1,disk101 entry. It tells us that we have to copy the disk1 file from d1 (which is \I386 as we discovered before) and copy it to our bootfolder using the name disk101. The second one d1,ntdetect.com, would also be copied from I386, but because no destination name is specified it will retain its current name. And lastly I want to point to FloppyFiles.3 where a couple of entries have folder names in their destination section. I'll leave it up to you to translate this to AutoIt code, but feel free to ask questions if something is unclear.

It's a bug in the MSFN guide. It should be:

I haven't tried it on x64, because I don't have one available to me. But if you could attach your dosnet.inf file, I'd be able to see if Microsoft changed anything that 'breaks' my tool. @johny_cale: Great to hear it worked for you.

I use the following part of my UA-DVD script to call my app: REM ------------------------------------------------------------------------------------------------------- REM --- Create BOOT Folders ------------------------------------------------------------------------------- REM ------------------------------------------------------------------------------------------------------- IF NOT EXIST E:\Work\PRO1 ( MD E:\Work\PRO1 ) START /wait E:\Tools\BootFolder.exe /u E:\Work\SETUP\XP\Professional\US\Attended\Base E:\Work\PRO1

Start those hotfixes with the /? parameter. It will give you the switches it supports.And as far as I know all post-SP2 hotfixes by Microsoft support the /integrate option. Integrating tools is something different altogether. It depends on the tools if and how these can best be integrated. You can integrate them into your pack as RyanVM did, or use the $OEM$ method, which I think is easier to learn. After install check the version number of the DLL's that got updated bij the hotfixes and compare those with the Microsoft knowledge base articles related to those hotfixes.Does this answer your questions?

So far there have been 20+ downloads, but only 1 reply. I was hoping for some more user experiences with it.

You could create a boot folder by hand, without the need of the boot.ini location or such, by parsing the dosnet.inf file from the Windows source. I made a small util which does that, but you could easily write something yourself with AutoIt. If you want to know how I did it, just PM me.

It's a problem with one of the hotfixes included in RyanVM's pack. You can read about it here. RyanVM posted a fix for this in that same topic here.

Did you select the option to Keep the Drivers? If you did, the \D folder won't be removed.

Couldn't it be that the file is stored in 1252 on his CD, but that Fedit fails because it automaticcaly tries to open it in the systems default codepage which differs from 1252.

And for an alternative way to create Boot Folders for NT4, 2000, XP and 2003 look at this topic.

A new Non-Critical XP SP2 Update: KB894391 -› FIX: DBCS attachment file names are not displayed in Rich Text e-mail messages and you may receive a "Generic Host Process" error message after you install security update MS05-012. Download -› 2029 KB (May 18, 2005) Switches: KB894391.exe /q /n /z