Siginet

I'd like to post a comment... but I really have no idea what it is. hehe. Is there any way I can help with the new project?

It was a very simple gui to make. But I think it is handy. Glad you like it Bashrat.

This is a very simple gui I made for "SetDevicePath.exe" which will allow you to browse to a directory containing a bunch of drivers. Then you can set your Windows XP to look for new drivers within that directory. When you are finished you just click on the "RESET" button and your Driver Path will be set back to normal. It is nothing much. I made it for myself... But maybe it will be useful to someone besides me. I haven't had a chance to thouroughly test it yet... but it should work fine if I understand how "SetDevicePath.exe" works correctly. So please let me know if it works ok or not. Enjoy. Path Changer Beta v0.1

WinME is one of the worst Windows OSes ever made. I agree with most when I say go WinXP. I also would recomend bumping up your memory though. I would recommend 512 MB RAM or at least 256 MB RAM.

Really?? So is this something BartPE can't do? So WinPE will allow us to Boot to different ISO's? Not mount an ISO within WinPE and use it inside WinPE?

Wouldn't it be as easy as putting the cd in the computer after the system is booted up, Allow autorun to open the setup window, Choose setup Windows XP Pro, Choose to Upgrade, and follow instructions? Or am I missing something? Can XP Home OEM not upgrade to XP Pro Retail? All or pretty much all of his programs would work fine after an upgrade.

Glad you got it working. I was going to suggest that you make sure your "install" directory was in the "$1" directory inside of the "$OEM$" directory. $OEM$\$1\install

A good way to learn batch files is using the /? switch after an exe. A lot of them will show you some switches you can use.

Not that I know of. But you can use an ISO to install within Virtual PC or VMWare.

Yes it will allow you to put multiple versions of XP on a CD or DVD then it will allow you to create an optimized ISO which you can burn to CD/DVD with just about any CD/DVD burning software. You can have One with DPs One without and one normal version of each different XP cd. As for your Nlite question... any limitations that you had with the driverpacks would still be the same. Also... you would probably need to use Nlite on the source files before using PowerPacker. I have plans on adding an option in the program to get rid of unneeded Update directories which will save space and also options to get rid of the LANG folder. But I haven't implemented it yet. The program was made to simplify making multiboot XP disks with/without driverpacks. Enjoy

May be bad media. I have had issues like this where if I only use a portion of the disk it works allright but when I use most of the disk it doesn't work. Try burning the disk slower... or different media. I wouldn't think adding a Programs directory to a good disk would cause a problem... unless I'm missing something.

Don't know why I thought it worked for me in the past. But this would work. If FileExists ("C:\WIN51") Then EnvSet ("CDROM", "C:\") EndIf If FileExists ("D:\WIN51") Then EnvSet ("CDROM", "D:\") EndIf If FileExists ("E:\WIN51") Then EnvSet ("CDROM", "E:\") EndIf If FileExists ("F:\WIN51") Then EnvSet ("CDROM", "F:\") EndIf If FileExists ("G:\WIN51") Then EnvSet ("CDROM", "G:\") EndIf If FileExists ("H:\WIN51") Then EnvSet ("CDROM", "H:\") EndIf If FileExists ("I:\WIN51") Then EnvSet ("CDROM", "I:\") EndIf If FileExists ("J:\WIN51") Then EnvSet ("CDROM", "J:\") EndIf If FileExists ("K:\WIN51") Then EnvSet ("CDROM", "K:\") EndIf If FileExists ("L:\WIN51") Then EnvSet ("CDROM", "L:\") EndIf...

Another update released. See original thread for more info.

New update added today. We may be getting close to a full release allready. Please try the new release out and let me know if you have any troubles. It should be much faster now. Thanks to Nazgul's BootFolder.exe program!

I have had bad experiances with using the command @ScriptDir in my autoits... maybe that is the same issue you are having. Sometimes if you use @ScriptDir in an autoit and call that autoit from a batch file which lies elsewhere it looks at the batch files destination as the current directory and then you run into problems. I have gotten into the habit of using this code... AutoItSetOption ( "ExpandEnvStrings", 1 ) RunWait(@ComSpec & " /c for %%i in (C D E F G H I J K L M N O P Q R S T U V W X Y Z) do if exist %%i:\WIN51 set CDROM=%%i:", "", @SW_HIDE) It is the same code others use in their batch files to set an environment variable "%CDROM%" to point to their UACD. This way you can put your apps on your cd and not have them copied to the HD. Also you can point directly to the file instead of using @ScriptDir. Try that... it may help you.

I think if you don't allready have a winnt.sif file it creates one for you. I could be wrong... I never actually tried it. If it doesn't that would be a good addition.

I think winrar supports 7zip. At least mine does. What version are you using?

Thanks Nazgul I appreciate it.

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. <{POST_SNAPBACK}> So the [FloppyFiles.?] sections are the only sections we need to grab files from, if I understand you correctly? Would you mind if I integrate your program within mine at least untill I get a chance to write an autoit that does this? It looks like it might take me a little while to write this. But from what you say it doesn't really sound too hard... it's just finding the time to do it. Thanks a lot Nazgul.

I wonder if it has anything to do with using a different language? I don't think it should matter. Weird it only does this with runonce. Runonce method seems to work out best for me. Did you use nlite or anything else before doing the driverpacks?

That app does exactly what I need. How did you parse the dosnet.inf file?

Fixed a major bug. V1.04 released

Windows XP PowerPacker v1.04 Released - 05-22-05 1. Fixed problem with Boot directory not copying to the destination sometimes. It should work every time now. Thanks go to: Swe_mx for pointing out this major bug.

Is the boot folder resideing on the same drive as your "boot.ini" file? I assumed that this folder would always be on the same drive as the "boot.ini" file. I am probably wrong though. It probably copys the boot files to a HD with the most space. I will fix this issue in the next version. Instead of having it look on the same drive as "boot.ini" I will have it check every drive for it. I should have done that to begin with anyways. Thanks for the report... I didn't think about that.

what program is it? BartPe/WinPE use the registry on the CD which makes it read only. There are plugins which will allow you to use a lot of the registry as writeable... but I think Windows Installer Service uses a part of the registry which is not writeable. There are a lot of things you can do in a PE disk... but there are limitations.