• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
kal

Issues with Setup

21 posts in this topic

Hi there,

Thank you for this nice script, it's highly appreciated :)

By the way, I've tried to make an install from an external usb Hard Drive, with a first 1900MB partition as required. But after I format my SSD during setup, setup complains that my external hard drive is corrupted.

Here is a picture :

img0764vp5.th.jpg

Someone has this issue?

Kal

Edited by kal
0

Share this post


Link to post
Share on other sites

Ok I've solved the problem, that's simply because I didn't choose the right type of usb-drive in USB_MultiBoot2.cmd. :thumbup

Kal

0

Share this post


Link to post
Share on other sites
But after I format my SSD during setup, setup complains that my external hard drive is corrupted.

In the Menu Screen did you use Option 0) to Change the Setting in USB-Harddisk instead of USB-stick ?

Because that makes that rdummy.sys is used and this is essential for using USB-Harddisk.

rdummy.sys makes Fixed USB-Harddisk seen in XP Setup as Removable Device.

Read more about it in the Help File.

Another thing which is however not causing your problem:

I saw that your USB-Drive is having Drive Letter U:

which means that you probably have given Answer Yes for Changing migrate.inf

at the end of the Program, whereas your answer for USB-Harddisk should be No.

wimb

0

Share this post


Link to post
Share on other sites

Yes, thank you wimb, i've just noticed it. It works like a charm now :)

Kal

Edited by kal
0

Share this post


Link to post
Share on other sites

I have another strange issue. In the menu screen, if I set the XP Source path as a virtual CDROM with ISO image mounted, then it works correctly. But if I choose a directory on my hard disk whith xp setup files, then i get a bsod before select the partition to format with this error: PROCESS1_INITIALIZATION_FAILED.

Ane idea ?

0

Share this post


Link to post
Share on other sites

I assume this happens during Text mode of setup, and if you use as source mounted ISO it doesn't happen, right? Something like 0x0000006B on that blue screen? Could you be more detailed please.

If that's true, then are source on virtual CD and on hard drive 100% identical?

Were both installs on the same hardware?

Have you tried to redo the preparation from your hard drive?

Edited by ilko_t
0

Share this post


Link to post
Share on other sites
I assume this happens during Text mode of setup, and if you use as source mounted ISO it doesn't happen, right? Something like 0x0000006B on that blue screen? Could you be more detailed please.

If that's true, then are source on virtual CD and on hard drive 100% identical?

Were both installs on the same hardware?

Have you tried to redo the preparation from your hard drive?

Here is a screenshot of the bsod :

img0758ah7.th.jpg

The source are exactly identical : I just make an iso of my unattended XP with RVM Integrator and mount it in a virtual CDROM. These installs were performed on a Asus eeePC. It happens with USB Hard-Disk and USB stick.

Kal

Edited by kal
0

Share this post


Link to post
Share on other sites

It seems that files inside $OEM$ folder are not copied to hard drive during installation, is it an issue ? I think it's normal because we can't use [unattended] section in WINNT.SIF and so the OemPreinstall variable is not set to 'Yes'. Am i right?

0

Share this post


Link to post
Share on other sites
It seems that files inside $OEM$ folder are not copied to hard drive during installation, is it an issue ? I think it's normal because we can't use [unattended] section in WINNT.SIF and so the OemPreinstall variable is not set to 'Yes'. Am i right?

Allthough the [unattended] Section is removed, we can do still an Unattended Install.

In the [Data] Section we have unattendswitch=yes

For Unattended Install you only have to fill in your Product key in the winnt.sif file of USB_MultiBoot2 folder.

$OEM$\CMDLINES.TXT is used for making UserAccounts and Install of Registry Tweaks at T-12

I think $OEM$ Folder has nothing to do with your present problem.

Check in the [Data] section the value of MsDosInitiated="1" , must be 1 for Install from USB.

It should be 1 for Install from Harddisk, a value of 0 is used for Install from CD.

Did you use the winnt.sif file provide with USB_MultiBoot2.zip ?

wimb

0

Share this post


Link to post
Share on other sites
It seems that files inside $OEM$ folder are not copied to hard drive during installation, is it an issue ? I think it's normal because we can't use [unattended] section in WINNT.SIF and so the OemPreinstall variable is not set to 'Yes'. Am i right?

Allthough the [unattended] Section is removed, we can do still an Unattended Install.

In the [Data] Section we have unattendswitch=yes

For Unattended Install you only have to fill in your Product key in the winnt.sif file of USB_MultiBoot2 folder.

$OEM$\CMDLINES.TXT is used for making UserAccounts and Install of Registry Tweaks at T-12

I think $OEM$ Folder has nothing to do with your present problem.

Check in the [Data] section the value of MsDosInitiated="1" , must be 1 for Install from USB.

It should be 1 for Install from Harddisk, a value of 0 is used for Install from CD.

Did you use the winnt.sif file provide with USB_MultiBoot2.zip ?

wimb

Iused my winnt.sif, and adapted DATA section with the one from USB_MultiBoot2.zip. The install is still unattende, it's juste that files inside $OEM$\$1 and $OEM$\$$ are not copied to hard disk drive, simply because OemPreinstall is not set to yes. MsDosInitiated is set to 1 of course, I didn't modify it. I'm gonna try to use Unattended section in WINNT.SIF to see if it's possible.

Kal

0

Share this post


Link to post
Share on other sites

I've tested with [unattended] section, but it shows an error screen saying that destination disk doesn't have enough space avalaible, just before to choose partition. But, I can continue to choose the right partition and then it works, files in $OEM\$1 and $OEM\$$ are copied. Here is [DATA] and [unattended] section :

[Data]
AutomaticUpdates="No"
Autopartition=0
UnattendedInstall="Yes"
MsDosInitiated="1"
floppyless="1"
UseSignatures="no"
EulaComplete="1"
winntupgrade="no"
win9xupgrade="no"
unattendswitch=yes

[Unattended]
UnattendMode=FullUnattended
UnattendSwitch="Yes"
FileSystem=*
WaitForReboot="No"
NoWaitAfterTextMode=1
NoWaitAfterGUIMode=1
DriverSigningPolicy=Ignore
NonDriverSigningPolicy=Ignore
Hibernation="No"
OemPreinstall=Yes

If I removethe unattended section, i don't have the error screen anymore, but files are not copied. It's simply because OemPreinstall=Yes is not defined, I guess.

Are you experiencing the same problem?

Kal

Edited by kal
0

Share this post


Link to post
Share on other sites

kal, it's somehow limitation. However, there are number of ways to copy files/folders during setup using:

1. txtsetup.sif

A command or batch script in/called from

2. presetup.cmd

3. svcpack.inf

4. cmdlines.txt

5. SetupParams in winnt.sif

6. GUIRunOnce and RunOnceEX in winnt.sif

http://unattended.msfn.org/unattended.xp/ could be a good place for reference.

About the limitation- in my tests I could not prevent Setup attempts to install on USB drive, when even a single line in [unattended] is present.

If there is not required space on USB drive you are lucky- you get an error message and can change partition, but if there is- Setup installs windows on the USB drive, usually changing the bootsector, which we do not want. That's why we remove the whole [unattended] section.

From ref.chm [data]:

Installs Windows to the first available partition that has adequate space for a Windows installation and does not already contain an installed version of Windows.

AutoPartition = 1

Either omit the AutoPartition entry from your answer file or set the value of AutoPartition to 1. If AutoPartition = 1, the /tempdrive command-line option of Winnt32.exe is ignored during Setup. If you do not set the value, text-mode Setup installs Windows on the partition where $WIN_NT$.~LS is located.

But even with AutoPartition = 0 or without this line, the presence of $WIN_NT$.~LS and any data in [unattended] seems to trigger Setup not to ask about destination partition. If someone finds a better way I'll be more than happy to use it.

About the 0X0000006B message- honestly I have no clues, apart from bad file during copying from hard drive. Do you amend winnt.sif in the same way when source is virtual CD and hard drive? Does the path to USB_MultiBoot2 folder contain spaces? I think Wimb fixed that already and you may need to redownload USB_MultiBoot2.cmd.

0

Share this post


Link to post
Share on other sites

Thanks a lot for your answer ilko_t.

I'm gonna use cmdlines.txt to copy the files i need, instead of $OEM$ folder. Indead, if we add just a line in [unattended], then it tried to auto partition, even if AutoPartition=0 is defined. Maybe a bug from installer... Not important, I will skip [unattended] section and use a batch file in cmdlines.txt to copy what I need.

About the 0X0000006B message, all files are correct. No problem, I'll continue to do the ISO before.

Kal

0

Share this post


Link to post
Share on other sites

You are welcome.

For copying files/folders a quick way is just to amend ren_fold.cmd, which is started by SetupParams, 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:

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

0

Share this post


Link to post
Share on other sites
You are welcome.

For copying files/folders a quick way is just to amend ren_fold.cmd, which is started by SetupParams, 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:

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

Ok, I'll do it.

It seems i've noticed, this time, a real bug in USB_MultiBoot2. Indeed, i've noticed that some files were not copied in $WIN_NT$.~LS\I386 : ren_fold.cmd, undoren.cmd and rdummy.sys.

So why these files are missing ? These files are copied in the command line :

xcopy %usb_temp%\$WIN_NT$.~LS\*.* %usbdrive%\$WIN_NT$.~LS\ /i /k /e /y /h | tee.bat -a usb_prep.log

So I've checked the output to see what was going on...

usb_xpbt\$WIN_NT$.~LS\$OEM$\acpi.msi
usb_xpbt\$WIN_NT$.~LS\$OEM$\cmdlines.txt
usb_xpbt\$WIN_NT$.~LS\$OEM$\cmdow.exe
usb_xpbt\$WIN_NT$.~LS\$OEM$\RunWPI.cmd
usb_xpbt\$WIN_NT$.~LS\$OEM$\SPTD.exe
usb_xpbt\$WIN_NT$.~LS\$OEM$\tweaks.cmd
usb_xpbt\$WIN_NT$.~LS\$OEM$\$$\system32\cmdow.exe
usb_xpbt\$WIN_NT$.~LS\I386\binifix4.cmd
usb_xpbt\$WIN_NT$.~LS\I386\presetup.cmd
Access denied

Humm, it failed on presetup.cmd which belongs to BTS DriverPacks. So all remainings files, which in my case are ren_fold.cmd/undoren.cmd/rdummy.sys, were not copied. I check the attributes of presetup.cmd file in $WIN_NT$.~LS\I386 and it's read only. Adding "/r" switch to the command line solved the problem :

xcopy %usb_temp%\$WIN_NT$.~LS\*.* %usbdrive%\$WIN_NT$.~LS\ /i /k /e /y /h /r | tee.bat -a usb_prep.log

Kal

Edited by kal
0

Share this post


Link to post
Share on other sites
Humm, it failed on presetup.cmd which belongs to BTS DriverPacks. So all remainings files, which in my case are ren_fold.cmd/undoren.cmd/rdummy.sys, were not copied. I check the attributes of presetup.cmd file in $WIN_NT$.~LS\I386 and it's read only. Adding "/r" switch to the command line solved the problem :

xcopy %usb_temp%\$WIN_NT$.~LS\*.* %usbdrive%\$WIN_NT$.~LS\ /i /k /e /y /h /r | tee.bat -a usb_prep.log

Thanks for your feedback.

In my case presetup.cmd was never read only, but I changed the program so that this problem is solved.

The new version has been Uploaded today.

wimb

0

Share this post


Link to post
Share on other sites

ok prior to reading this thread, i tried to merge my winnt.sif (unattended) with the winnt.sif which is created by the program.

i have exactly the issues described above.

here (http://www.msfn.org/board/install-usb-winsetupfromusb-gui-t120444.html) in the first post it is mentioned that presetup.cmd is taking care of this problem.

however i can't find any indication regarding the unattend issue.

my presetup.cmd looks like this:

SET TAGFILE=\$WIN_NT$.~LS
FOR %%h IN (U D M N O P Q R S T V W X Y) DO IF EXIST "%%h:%TAGFILE%" SET CDDRIVE=%%h:
if "%CDDRIVE%" == "" (
FOR %%h IN (C E F G H I J K L) DO IF EXIST "%%h:%TAGFILE%" SET CDDRIVE=%%h:
)

REM ===========Added by WinSetupFromUSB============
IF EXIST %systemroot%\system32\setupold.exe DEL /F %systemroot%\system32\setupold.exe
IF EXIST c:\boot.003 DEL /F c:\boot.003
REM ====================END=======================
EXIT

so here is my question:

since i cannot use the [unattended] section in winnt.sif, where can i specify those values, settings, etc. ??

any hint?

thx

Edited by theUnattender
0

Share this post


Link to post
Share on other sites

What version of WinSetupFromUSB did you use?

There should be more lines in presetup.cmd if any of the latest was used, unattended section should be fully supported, with some workarounds done by the program.

Edited by ilko_t
0

Share this post


Link to post
Share on other sites
What version of WinSetupFromUSB did you use?

There should be more lines in presetup.cmd if any of the latest was used, unattended section should be fully supported, with some workarounds done by the program.

my bad .. i got here via a german site which had WinSetupFromUSB_0-1-1

on the original thread it's Latest - vers. 0.2.3 - 06.July.2009

i will try it with the new version ;-)

thx

0

Share this post


Link to post
Share on other sites

ok vers. 0.2.3 did the trick.

unattended worked as expected.

no extra configuration needed.

great software !!

thx

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.