*FIXED*

Hello. I am using the USB_MultiBoot3 program, and it works very well for transferring the setup files to the USB-stick and making a multiboot menu for the setup files. I am interested in getting it to multiboot FreeDOS and bartPE(or MiniPE) as well, but the package only includes the bootsectors for freeDOS and bartPE, and I dont know where to place the files for these to get them included.

I found a reference to FreeDOS setup in the help files, and copied fdubcd.img to the images folder in MULTI_CONTENT folder. but if i select MULTI_CONTENT in the setup menu instead of X_CONTENT folder I get an error message(the path [my path here] does not contain USB Content Source Files). I still allows me to use that directory however after the error message, and everything installs as if i had used the X_CONTENT files with no grub files included, no FreeDOS files included... it looks just like using the X_CONTENT folder to my untrained eye... can someone maybe let me know how i might include some of the extra multiboot options or point me in the direction to figure this out? Thanks

I'm currently only interested in having the Setup TXT and GUI selections as well as FreeDOS. a bartPE or miniPE would be an added bonus only.

*FIXED*

Edited February 22, 200818 yr by ineptspelr

This subject problem has been resolved with a fresh extraction from USB_MultiBoot4.

I am now getting the multiboot options that I want when selecting the multi_content folder. I assume that I must have slagged my first folder somehow.

I am still having one problem, and that's that the files in the $OEM$\$Docs and OEM$\$$ are not getting copied over during the install. They end up on the flash drive in the $WIN_NT$.~LS folder, but don't get transferred during the windows install. (for example: I want to add a file to the startup folder. I placed it in the location U:\$WIN_NT$.~LS\$OEM$\$Docs\All Users\Start Menu\Programs\Startup , but it does not end up in that folder after install)

I will continue to plug away at it in the hopes that this is a similar issue to my first one and that i somehow managed to corrupt the install. Any suggestions would be helpful though. Using the $OEM$ folder would be much easier for updating reasons, but I guess i could use some other method of copying like txtsetup. Thanks for help in advance.

Edited February 22, 200818 yr by ineptspelr

I am still having one problem, and that's that the files in the $OEM$\$Docs and OEM$\$$ are not getting copied over during the install. They end up on the flash drive in the $WIN_NT$.~LS folder, but don't get transferred during the windows install. (for example: I want to add a file to the startup folder. I placed it in the location U:\$WIN_NT$.~LS\$OEM$\$Docs\All Users\Start Menu\Programs\Startup , but it does not end up in that folder after install)

This is explained in the Help_USB_MultiBoot4.txt file point 5.

- $OEM$ Folders are Not Copied - This is Normal for Install of XP from USB

Files in $OEM\$1 and $OEM\$$ folders are NOT copied in this case.

For copying files/folders a quick way is just to amend ren_fold.cmd,

which is started by SetupParams in winnt.sif,

we use it to temporary rename folders on stick before end of GUI mode,

preventing long wait when Setup attempts to delete them.

Simply add your commands right above these lines in ren_fold.cmd

ren_fold.cmd - partly

ren %USBDRIVE%\txtsetup.sif txtsetup.bak
ren %USBDRIVE%\$WIN_NT$.~BT WIN_NT.BT
ren %USBDRIVE%\$WIN_NT$.~LS WIN_NT.LS

I will change ren_fold.cmd such that $OEM$ Folders will be copied as normally expected.

Next release will have these changes.

wimb

Edited February 22, 200818 yr by wimb

Thanks for the quick reply. Is there a way to execute a cmd file before the end of the GUI setup. If i'm not mistaken, SetupParams executes at the end of the install.

EDIT: I think i'm going to try to edit presetup.cmd to do the file copies that i want. I will need an item copied to the windows folder for a later part of the install.

Edited February 22, 200818 yr by ineptspelr

http://unattended.msfn.org/unattended.xp/view/web/13/ :

» GUI-mode Setup

1. DetachedProgram executes from winnt.sif at T-39 stage

2. Installs Devices

3. Installs Network

4. Installs Start Menu Items

5. Registers Components

6. svcpack.inf executes at T-13 minute stage

7. cmdlines.txt executes at T-12 minute stage

8. SetupParams executes from winnt.sif at T-9 minute stage

9. Saves Settings

10. Deletes temporary files then reboots...

Isn't 8 early enough for your needs? I'd rather not touch presetup.cmd, unless you are aware that and how it is used by BTS drivers pack.

I wonder, the subforum is new, here are like 10-15 threads only on a single page, couldn't you see this thread with so informative title?

$OEM$ folders aren't being copied to %systemdrive%

and the answer here:

http://www.msfn.org/board/index.php?act=fi...&pid=734317

Edited February 22, 200818 yr by ilko_t

» GUI-mode Setup

1. DetachedProgram executes from winnt.sif at T-39 stage

2. Installs Devices

3. Installs Network

4. Installs Start Menu Items

5. Registers Components

6. svcpack.inf executes at T-13 minute stage

7. cmdlines.txt executes at T-12 minute stage

8. SetupParams executes from winnt.sif at T-9 minute stage

9. Saves Settings

10. Deletes temporary files then reboots...

Isn't 8 early enough for your needs? I'd rather not touch presetup.cmd, unless you are aware that and how it is used by BTS drivers pack.

No. SetupParams will not work. but I think you are correct about presetup. I should be able to execute a cmd file from cmdlines of my own creation, ya? From the name, I would assume the answer is yes. I will look at how to achieve my goals through cmdlines.txt.

Again, thanks for your quick replies.