Siginet

Back earlier when 5.05 was initially released mark said he would get this error: It is pretty much the same thing I have been getting everytime I try to use the Mass Storage Driver Pack. I don't get the error during slipstream method... I get it when I use winnt32.exe to create the boot directory for install. It says that it cannot find that file. It allows me to skip the file... but then asks me 2 more times for the file before it completes the process. That file is not in my I386 directory at all. Has anyone else encountered this error? Everything else seems to be working fine for me. I have gotten that error from 5.05 with and without the fixes and also in 5.05.1. Any ideas? Siginet

OK... here is an update to my progress: Everything is working great. It works better than I imagined it. The only thing I believe that is left is to implement cdimage.exe into it as well. Here is a quick layout of what it does: It opens a gui window that has a few input boxes, browse buttons, and radiobuttons. 1. First it asks you to browse to where your windows xp files are. 2. Next it asks for the destination you want to use for your multiboot cd. 3. It asks if you are using Professional or Home Edition. 4. It asks if it is a Corporate, Retail, OEM, or Upgrade copy. 5. It asks if you are using BTS DriverPacks. If you answer yes it enables you to browse and point to the "UWXPCD_ROOT" folder created by the "BTS_DPs_Slipstreamer_V***.cmd" file (Which has the file "RUN_ME.CMD"). 6. Then it asks if it is an unattended install or not. If you select Unattended then it enables you to point to the winnt.sif file you will be using. 7. At the bottom there is 3 buttons... [Package ISO Now] Which will be used in the very end when you are ready to compile your optomised ISO. [Pack Files] Which is the button you use to grab the files, create a boot directory, create a boot entry in the list, and hex edit needed boot files. (Almost completley Automated.) [About] The about button should be pretty self-explanitory. And eventually I will create a help button or something. When it is released it will probably have bugs in it that I didn't see... but that is what beta testing is all about. Another nice feature is that when it is getting the boot files for the boot directory it also protects your boot.ini file from getting messedup. I will work on finishing this app tonight and hopefully post a link for everybody by this weeked when I am not so buisy. BTW I decided to call it "Windows XP PowerPacker." I'll try to post some screenshots later.

I started this thread. Do you need me to teach you how to use your computer? LOL! J/K!

I think you posted in the wrong thred muiz.

OK I found a good hex editor. It is coming together smoothly. Not much more before the initial release. I have a feelin you guys will like this.

I am in the process of createing an AutoitGui that will help people create a Windows XP Multiboot Disk. It will also have capability of running the BTS DriverPack Scripts in it. As of now it is pretty close to being released. When I release it I will need Beta testers and requests. But please be easy on me. This is my first program. Does anyone know of a good (Dos based) hex editer I could use in my program for Hex editing the boot files and setupldr.bin? That is pretty much the step where I am at right now.

WTF??!?? Have some patience! BTS is doing everything he can to make things work. He can't possibly do everything himself... he needs people to test the DPs on their systems as well so he can work out bugs. Their is a lot of different hardware in the world. What may work on one system might not work on another. In my opinion the DPs are coming along very well. with only a few minor bugs.

Not sure if this is the reason for the "afasttx2k.sys" error... but I noticed that if you extract the file "afasttx2k.sy_" you get a file named "fasttx2k.sys". Shouldn't it be "afasttx2k.sys"? Also I found a file called "fasttx2k.sy_" which also extracts a file called "fasttx2k.sys". I hope someone understands what I just wrote. You may need to read my post very carefully.

It definitly is in the i386 dir... but can't find it?? i checked back on my XPCD i created with v5.0.4.11 and there is no file named like that. So it's a new added thing. - same as usual - All (new) driverpacks except Wlan - Method 2 - keep the drivers. No installation done, ends before partition creating. If there is a quick "possible" solution, i'm able to do a another test now. Anyone? ( edit: Bâshrat, i know you can't sleep now.. ) ← I get the same error. I am using M3 Without KtD.

Great news! Thanks Bashrat!

Did you add an edited setup screen? Because that is the file that would have been edited.

I have XPE and BartPE on one multiboot disk. All I did was integrate both programs folders together. Before I made my XPE ISO I renamed the nu2menu folder to xpemenu. Then I edited the xpemenu.inf file so that it would create a seperate nu2menu folder upon creating the ISO. Both of my PE loads work 100%.

For one thing each command is numbered 95. So that will prob cause an issue.

Have fun.

I too have successfully done this. I actually have made a 700MB CD which has Win XP Pro Corp Win XP Pro Retail Win XP Pro OEM Win XP Pro Update Win XP Home Retail Win XP Home OEM Win XP Home Update Each OS has 3 different options. -Regular which is a normal install without any Driverpacks and nothing unattended -Unattended With Driverpacks -Unattended Without DriverPacks I also Integrated every Hotfix after SP2. And auto install all other Windows XP Updates. All of this fits on one CD. It is actually over 7 Gigs of information... but using "cdimage.exe" It is only 698MB! So far everything works flawlessly! I run my Graphics_Control_Panels.cmd, Sound_Control_Panels.cmd, and cleanup.cmd from the disk itself instead of from the systemdrive. The biggest thing to remember when using the Driverpacks this way is to make sure you have the txtsetup.sif and dosnet.inf files inside of the boot files directory (Example: PRO1) edited correctly with the setuporg.exe and presetup.cmd files. Also make sure the setuporg.exe and presetup.cmd files reside in each "I386" directory. Make sure your Winnt.sif files are in the boot directories as well. Your Driverpacks should be in the "OEM" folder on the root of your CD. Your "$OEM$" folders belong inside of the root directory for each OS (Along side of each I386 folder). Now it's time to make my DVD version of this disk! Thanks Bashrat and everyone else who is invoved. I've learned a lot from msfn.org.

I don't think there is much need for a modem pack either. Windows XP seems to install a lot of the modems by default in my experiances. If xp doesn't by default it almost allways installs from windows update. I think Bashrat's got the most important DP's covered. Chipset drivers would be a great addition.

Look in your I386 folder for a file called "txtsetup.sif" Inside the file do a search for "setuporg.exe" If you find this instance than this part should be good. Make sure you have a file called "presetup.cmd" in the I386 folder. You should have a folder called "OEM" on the root of your disk. (I don't mean $OEM$ I mean OEM.) Method 1 uses the $OEM$ folder for the driverpacks, Method 2 uses the OEM folder. Inside there you should see the driverpacks and a folder called "BIN". If you have verified these steps you should be good to go. There are a couple other steps... but that should just about cover it. Now burn an ISO and boot it up in VMWare to test it. Or burn it and try it on a computer.

Isn't their a PEHD install on the bart disk? I beleive there is a way to install bart to the hard disk so that you are given the option to boot into your os or the bart os. You would need to have the pehdinst plugin and you would have to burn an ISO onto the computer in some way. Mount the iso in a program like "Daemon Tools" and install it to the hard drive. Not sure if WinPE has the same thing.

Don't extract the 7zip files manually. Use the DriverPacksBase and follow the instructions. Click on the BTS_DriverPacks_BASE_V5029.exe file to extract it. Then place all of the driver pack .7z files in the "\DriverPacks" directory. Then run "BTS_DriverPacks_Slipstreamer_V5029.cmd" That will extract everything to a directory called "\UWXPCD_ROOT" Copy everything INSIDE of that directory to the root of the directory where your cd is being made (On the same level as \I386) Then run "\the Run***.cmd" sorry I don't remember what it's called. It will do everything for you. Just read the instructions carefully.

ThX

The Utility.exe error can be fixed by renaming the file the way I stated in my previous post. @BRTS After I renamed the files all went well using all DP. But upon first boot into windows (Using VMWare) It just hung at a black screen. I rebooted and it was normal.

I tried to run "BTS DriverPacks BASE V5.02.7" but it stops at: Compressing mgabg.exe... Utility.exe==CTZAPXX.exe was unexpected at this time. When I tried BTS DriverPacks BASE V5.02.6 I got an error in txtsetup.oem during text setup. Hope this info helps. ======== Update: I beleive the problem is in this directory: "DriverPack_Graphics_B_V502.7z\DP\G\M\2" There are 11 files that have a space in them. "Multi-Display Utility" I am gonna repack the 7z file and see if that fixes it.

Would "%homepath%\Desktop" "%homepath%\My Documents" work for you? Sorry I'm not sure exactly what you want to do... but this code should point to your docs & Desktop folders.

Does anyone know which files I should remove from the mass storage DP files to get it to work properly on most MB. I have no troubles with some MB but latley I have been getting issues with the blue screen of death during text setup on a few machines. The most recent one is the NV Sata Raid. I tried to read through the thread on how to fix this problem... but me being somewhat of a newbie in this area has made it kind of difficult to understand what all needs to be done. Can someone list in here all the known fixes that should be done before the next MassStorage pack is released? BTS has done a great job with these packs, and when it is used on a machine that it works on it is wonderful. ThX to all involved with this project. Siginet

And I think the $OEM$ folder needs to reside outside of the I386 folder.