[dforionstar]

ilko_t, on Feb 19 2009, 12:31 AM, said:

Sorry, I have no ideas. Maybe try removing UnattendedInstall="No"
Is the windows version the same as the one on the CD which repair install option worked?

I recall in the previous tests when Setup was performed from USB, repair install was possible, should the extra line in boot.ini was present. Maybe some entries in \windows\system32\$winnt$.inf, which differ from a CD install matter as well...

ilko_t: Thank you very much for your commitment and effort in trying to get this to work!

I have tried with UnattendedInstall="No", and UnattendedInstall="Yes". But for some reason, it seems Setup does not look for previous installations, and if so fails to provide the Repair screen. Or does so, so fast I cannot tell. Windows versions are the same. The extra line in the boot.ini gets removed every time during Setup, so I stopped using it.

I suppose I could copy the $winnt$.inf from the CD to the Flash Drive, but not sure how that would impact Multiboot?

Anyway, I successfully ran Setup:Repair from CD and am now working on the elusive VPN problem which was the whole reason for attempting a Repair in the first place.

Thanks again to All!

[dforionstar]

ilko_t, on Feb 19 2009, 01:59 AM, said:

@dforionstar

Try with only these entries in winnt.sif and nothing else:

[data]
floppyless="1"
msdosinitiated="1"

Make sure you are editing winnt.sif in ~BT folder.
Did you use USB_multiboot or WinSetupFromUSB ? If the latter, did you replace the modified by the program winnt.sif with your own, or created previously by USB_multiboot?

I used USB_multiboot, and replaced the winnt.sif on UFD with the modified one.

[Xeijin]

Does anyone know why this is not copying the contents of my $OEM$ folder along? It is causing my RunOnceEx program installations to fail.

Also DriverPacks seems to be broken (DriverPacks is not extracting the .7z archives at the start of setup like it normally does) I hear this all has something to do with a "presetup.cmd" file but it is no where to be found on the USB.

Can I not just add OEMPreinstall=1 back to the winnt.sif file?

Edit: OK seems that there is a presetup.cmd (located in the i386 directory in the "LS" folder) but it just doesnt seem to work? I dunno, can anyone help?

This post has been edited by Xeijin: 21 February 2009 - 06:40 PM

[ilko_t]

dforionstar- sorry we couldn't make it work from USB, but glad you made it from a CD

Xeijin- well, you should provide more details, like what are contents of presetup.cmd, is $OEM$ on the USB stick etc. etc.
Try to read your own post, how much useful information you could gather to help troubleshooting your problem?

[Xeijin]

Sorry about that, I've included the contents of presetup.cmd, it seems to be alright I'm just wondering if it actually gets executed?

 
SET TAG=\WIN51
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:%TAG%" SET CDDRIVE=%%i:
SET OEM=%CDDRIVE%\OEM

IF EXIST %OEM%\bin\7z.exe Copy /V /Y %OEM%\bin\7z.exe %SYSTEMROOT%\system32\7z.exe
IF EXIST %SYSTEMDRIVE%\bin\7z.exe Copy /V /Y %SYSTEMDRIVE%\bin\7z.exe %SYSTEMROOT%\system32\7z.exe
IF EXIST %OEM%\bin\un7zip.exe SET UN7ZIP=%OEM%\bin\un7zip.exe
IF EXIST %SYSTEMDRIVE%\bin\un7zip.exe SET UN7ZIP=%SYSTEMDRIVE%\bin\un7zip.exe

IF EXIST %OEM%\bin\DPsFnshr.ini Copy /V /Y %OEM%\bin\DPsFnshr.ini %SYSTEMDRIVE%\DPsFnshr.ini
IF EXIST %SYSTEMDRIVE%\bin\DPsFnshr.ini Copy /V /Y %SYSTEMDRIVE%\bin\DPsFnshr.ini %SYSTEMDRIVE%\DPsFnshr.ini
IF EXIST %OEM%\*.ins Copy /V /Y %OEM%\*.ins %SYSTEMDRIVE%\

IF EXIST %SYSTEMROOT%\system32\7z.exe (
	IF EXIST %OEM%\D*.7z 7z x -y -aoa %OEM%\D*.7z -o%SYSTEMDRIVE%
	IF EXIST %OEM%\bin\D*.7z 7z x -y -aoa %OEM%\bin\D*.7z -o%SYSTEMDRIVE%
	IF EXIST %SYSTEMDRIVE%\D*.7z 7z x -y -aoa %SYSTEMDRIVE%\D*.7z -o%SYSTEMDRIVE%
	IF EXIST %SYSTEMDRIVE%\bin\D*.7z 7z x -y -aoa %SYSTEMDRIVE%\bin\D*.7z -o%SYSTEMDRIVE%
	IF EXIST %OEM%\000_SR*.7z 7z x -y -aoa %OEM%\000_SR*.7z -o%SYSTEMROOT%
	IF EXIST %SYSTEMDRIVE%\000_SR*.7z 7z x -y -aoa %SYSTEMDRIVE%\000_SR*.7z -o%SYSTEMROOT%
	IF EXIST %OEM%\000_SD*.7z 7z x -y -aoa %OEM%\000_SD*.7z -o%SYSTEMDRIVE%
	IF EXIST %SYSTEMDRIVE%\000_SD*.7z 7z x -y -aoa %SYSTEMDRIVE%\000_SD*.7z -o%SYSTEMDRIVE%
) ELSE (
	IF EXIST %OEM%\D*.7z %UN7ZIP% %OEM%\D*.7z %SystemDrive%\
	IF EXIST %OEM%\bin\D*.7z %UN7ZIP% %OEM%\bin\D*.7z %SystemDrive%\
	IF EXIST %SYSTEMDRIVE%\D*.7z %UN7ZIP% %SystemDrive%\D*.7z %SystemDrive%\
	IF EXIST %SYSTEMDRIVE%\bin\D*.7z %UN7ZIP% %SystemDrive%\bin\D*.7z %SystemDrive%\
	IF EXIST %OEM%\000_SR*.7z %UN7ZIP% %OEM%\000_SR*.7z %SYSTEMROOT%\
	IF EXIST %SYSTEMDRIVE%\000_SR*.7z %UN7ZIP% %SYSTEMDRIVE%\000_SR*.7z %SYSTEMROOT%\
	IF EXIST %OEM%\000_SD*.7z %UN7ZIP% %OEM%\000_SD*.7z %SYSTEMDRIVE%\
	IF EXIST %SYSTEMDRIVE%\000_SD*.7z %UN7ZIP% %SYSTEMDRIVE%\000_SD*.7z %SYSTEMDRIVE%\
)

IF EXIST %SYSTEMDRIVE%\D*.7z DEL %SYSTEMDRIVE%\D*.7z
IF EXIST %SYSTEMDRIVE%\000_SR*.7z DEL %SYSTEMDRIVE%\000_SR*.7z
IF EXIST %SYSTEMDRIVE%\000_SD*.7z DEL %SYSTEMDRIVE%\000_SD*.7z

IF EXIST %OEM%\bin\DevPath.exe SET SDP=%OEM%\bin\DevPath.exe
IF EXIST %SYSTEMDRIVE%\bin\DevPath.exe SET SDP=%SYSTEMDRIVE%\bin\DevPath.exe
IF EXIST %SYSTEMDRIVE%\DSPdsblr.exe SET WDSP=%SYSTEMDRIVE%\DSPdsblr.exe
IF EXIST %SYSTEMDRIVE%\WatchDSP.exe SET WDSP=%SYSTEMDRIVE%\WatchDSP.exe
IF EXIST %CDDRIVE%\D SET DP=%CDDRIVE%\D
IF EXIST %SYSTEMDRIVE%\D SET DP=%SYSTEMDRIVE%\D

%SDP% %DP%
START %WDSP%

REM ===========Added by WinSetupFromUSB============
IF EXIST %systemroot%\system32\setupold.exe DEL /F %systemroot%\system32\setupold.exe
IF EXIST %CDDRIVE%\$WIN_NT$.~LS\$OEM$\$1\nul xcopy %CDDRIVE%\$WIN_NT$.~LS\$OEM$\$1\*.* %systemdrive%\ /i /k /e /r /y /h
IF EXIST %CDDRIVE%\$WIN_NT$.~LS\$OEM$\$$\nul xcopy %CDDRIVE%\$WIN_NT$.~LS\$OEM$\$$\*.* %systemroot%\ /i /k /e /r /y /h
IF EXIST %CDDRIVE%\$WIN_NT$.~LS\$OEM$\$Progs\nul xcopy %CDDRIVE%\$WIN_NT$.~LS\$OEM$\$Progs\*.* "%systemdrive%\Program Files\" /i /k /e /r /y /h
type %systemroot%\system32\tempunat.inf >> %systemroot%\system32\$winnt$.inf
IF EXIST c:\boot.003 DEL /F c:\boot.003
REM ====================END=======================
EXIT 

Additionally, both the $OEM$ and OEM folders are present on the USB Stick (In the LS directory) and both contain the correct contents, but nothing seems to be done with them.

Thanks in Advance.

This post has been edited by jaclaz: 22 February 2009 - 01:13 PM

[ilko_t]

Compare USB_stick\~LS\I386\setup.ex_ with \WinSetup\files\winsetup\setup.ex_, are they the same? If not- copy the latter to the USB stick.
The program checks presence of BTS OEM folder and does not copy the modified setup.exe (which launches presetup.cmd) in such case, assuming it had been already replaced by BTS integrator. Maybe you still have the original setup.exe, curious why it was not the fake one, if that's the case.
WinSetupFromUSB log files may help revealing what has happened. Check the first post in this thread for the latest and the backed up logs location.

[jezza333]

ilko_t, on Feb 6 2009, 08:40 PM, said:

Thanks jaclaz.

I've just excluded menu.lst from the files being copied, no matter from what source. This should fix unexpected problems later on, should more and more items included start using grub4dos.
Entries in menu.lst to start the various items are added by WinSetupFromUSB anyway. May also add merging menu.lst if found, with the one created by the program.

Maybe you could use the menu from VistaPE over that of the current XP installer. It's much smoother graphically [uses the face background], and all that has to be done [as jaclaz also mentioned] is appending entries to the list.

EDIT: Any plans to add support for multiple 'distros' under the one category [ie VistaPE + Vista installation DVD on the one medium]?. I have done it manually by creating partitions and just changing GRUB's menu file, but it would be that little bit nicer if it was integrated. In any case, it's no problem. A little legwork never hurts

This post has been edited by jezza333: 22 February 2009 - 06:32 PM

[Xeijin]

ilko_t, on Feb 22 2009, 10:06 PM, said:

Compare USB_stick\~LS\I386\setup.ex_ with \WinSetup\files\winsetup\setup.ex_, are they the same? If not- copy the latter to the USB stick.
The program checks presence of BTS OEM folder and does not copy the modified setup.exe (which launches presetup.cmd) in such case, assuming it had been already replaced by BTS integrator. Maybe you still have the original setup.exe, curious why it was not the fake one, if that's the case.
WinSetupFromUSB log files may help revealing what has happened. Check the first post in this thread for the latest and the backed up logs location.

Well the file in the WinSetupFromUSB directory was indeed different to the one on the USB, however overwriting it does not seem to have made a difference.

I have also just realised that this might perhaps be related but, when the GUI portion of the setup begins, where the Driverpacks extraction would normally take place (i.e. the light blue screen where you can see only the cursor) shows for a few seconds, before launching straight into the "billboard" setup screens

However, I also get a Command Prompt appear showing:

Microsoft Windows XP [Version 5.1.2600]
<C> Copyright 1985-2001 Microsoft Corp.

C:\WINDOWS\system32>

I tried typing "presetup.cmd" at this prompt at which point I get a scrolling list of commands, implying that it is running the presetup.cmd, but it doesnt seem to do anything else (I.e. I do not see the unzipping of .7z files as I normally would) not that this is all taking place while normal installation is continuing in the background...

(Note that this was happening before as well as after I copied an setup.ex_ files as you suggested, I didn't realise until now that the two may perhaps have been connected)

On the case of the log file, there seems to be rather alot inside of it, is there a specific phrase i can search for? Or should I upload the log and link to it?

Thanks again.

This post has been edited by Xeijin: 22 February 2009 - 06:58 PM

[mhike]

hello there,
i am a newbie with regard to this. I would like to boot from usb, and put a Vista installer instead of xp?
What is the easiest way that I could do so that I can install vista from USB to HD, I have a 4g pendrive.
Any help will be greatly appreciated. Thanks. Have a nice day.

[ilko_t]

jezza333, on Feb 22 2009, 04:22 PM, said:

Maybe you could use the menu from VistaPE over that of the current XP installer. It's much smoother graphically [uses the face background], and all that has to be done [as jaclaz also mentioned] is appending entries to the list.

EDIT: Any plans to add support for multiple 'distros' under the one category [ie VistaPE + Vista installation DVD on the one medium]?. I have done it manually by creating partitions and just changing GRUB's menu file, but it would be that little bit nicer if it was integrated. In any case, it's no problem. A little legwork never hurts

That would require a lot of changes, so no such plans any soon.

Xeijin, on Feb 22 2009, 04:38 PM, said:

ilko_t, on Feb 22 2009, 10:06 PM, said:

Compare USB_stick\~LS\I386\setup.ex_ with \WinSetup\files\winsetup\setup.ex_, are they the same? If not- copy the latter to the USB stick.
The program checks presence of BTS OEM folder and does not copy the modified setup.exe (which launches presetup.cmd) in such case, assuming it had been already replaced by BTS integrator. Maybe you still have the original setup.exe, curious why it was not the fake one, if that's the case.
WinSetupFromUSB log files may help revealing what has happened. Check the first post in this thread for the latest and the backed up logs location.

Well the file in the WinSetupFromUSB directory was indeed different to the one on the USB, however overwriting it does not seem to have made a difference.

I have also just realised that this might perhaps be related but, when the GUI portion of the setup begins, where the Driverpacks extraction would normally take place (i.e. the light blue screen where you can see only the cursor) shows for a few seconds, before launching straight into the "billboard" setup screens

However, I also get a Command Prompt appear showing:

Microsoft Windows XP [Version 5.1.2600]
<C> Copyright 1985-2001 Microsoft Corp.

C:\WINDOWS\system32>

I tried typing "presetup.cmd" at this prompt at which point I get a scrolling list of commands, implying that it is running the presetup.cmd, but it doesnt seem to do anything else (I.e. I do not see the unzipping of .7z files as I normally would) not that this is all taking place while normal installation is continuing in the background...

(Note that this was happening before as well as after I copied an setup.ex_ files as you suggested, I didn't realise until now that the two may perhaps have been connected)

On the case of the log file, there seems to be rather alot inside of it, is there a specific phrase i can search for? Or should I upload the log and link to it?

Thanks again.

This is weird behavior I've never seen. As you can see the section in presetup.cmd added is at the bottom and should not affect the entries above it. No idea why the modified setup.exe does not launch presetup.cmd automatically either
Does SetupORG.exe exist in the XP source? Maybe BTS guys made some changes to their integrator...
How it was before- original setup.exe is renamed to setupORG.exe and replaced by a fake one, which executes presetup.cmd and then launches the original setup.exe in order to continue GUI mode. If WinSetupFromUSB finds setupORG.exe it does not copy the fake setup.exe, if not- the original setup.exe is extracted and renamed to setupORG.exe and the fake one is copied to ~LS\I386\.
As for the log files- please put them all in a zip archive and upload them somewhere.

mhike, on Feb 22 2009, 08:43 PM, said:

hello there,
i am a newbie with regard to this. I would like to boot from usb, and put a Vista installer instead of xp?
What is the easiest way that I could do so that I can install vista from USB to HD, I have a 4g pendrive.
Any help will be greatly appreciated. Thanks. Have a nice day.

Format the USB stick with HP USB format tool using NTFS. Select Vista setup checkbox, browse and give the Vista source path, then click GO. That's all.

[Xeijin]

ilko_t, on Feb 23 2009, 08:15 AM, said:

This is weird behavior I've never seen. As you can see the section in presetup.cmd added is at the bottom and should not affect the entries above it. No idea why the modified setup.exe does not launch presetup.cmd automatically either
Does SetupORG.exe exist in the XP source? Maybe BTS guys made some changes to their integrator...
How it was before- original setup.exe is renamed to setupORG.exe and replaced by a fake one, which executes presetup.cmd and then launches the original setup.exe in order to continue GUI mode. If WinSetupFromUSB finds setupORG.exe it does not copy the fake setup.exe, if not- the original setup.exe is extracted and renamed to setupORG.exe and the fake one is copied to ~LS\I386\.
As for the log files- please put them all in a zip archive and upload them somewhere.

ilko_t,

I have uploaded the log file of the last time I used WinSetupUSB to create the bootable stick, I've uploaded it here:

http://www.mediafire.com/?wwylmmwymmm

I can confirm that setupORG.exe is present in both the i386 folder in my source, and the USB stick.

This post has been edited by Xeijin: 23 February 2009 - 03:10 AM

[ilko_t]

Here it is:
presetup.cmd:

SET TAG=\WIN51

This file is not copied by default. In the previous BTS integrators the tag was \OEM folder.
You may copy back setup.ex_ from your XP source to ~LS\I386\ and WIN51 to USB root, or change presetup.cmd to SET TAG=\OEM.
Hopefully this will resolve all the issues.
I will make the required changes in the program, thanks for reporting

[mhike]

Thanks for the tip ilko t. Ill try that later. I also have another query. I was able to create an xp installer to usb using the winsetup from usb. I was able to install xp successfully from the usb to HD. However, when I restarted the pc after completing the installation processes, and unplugged the source usb, the pc could not boot anymore. I already changed the boot order in bios. Windows xp was already installed to the HD. It displays something like boot or hardware error. When I inserted the usb again to boot from it, it displays a hal.dll error. What should I do?thanks in advance. have a nice day.

[ilko_t]

Have a look at this topic and the links within:
http://www.msfn.org/...howtopic=128303

Look at the FAQs as well. This is the most common situation and has been discussed many many times

[jaclaz]

Just for the record, and to cheer up a bit ilko_t , read what Cedrick "Nitch" Collomb (Author of unlocker) :
http://ccollomb.free.fr/unlocker/

has to say about WinsetupfromUSB:
http://ccollomb.free.fr/blog/?p=59

And also this :
http://ccollomb.free.fr/blog/?p=61

jaclaz

[Xeijin]

ilko_t, on Feb 23 2009, 09:44 AM, said:

Here it is:
presetup.cmd:

SET TAG=\WIN51

This file is not copied by default. In the previous BTS integrators the tag was \OEM folder.
You may copy back setup.ex_ from your XP source to ~LS\I386\ and WIN51 to USB root, or change presetup.cmd to SET TAG=\OEM.
Hopefully this will resolve all the issues.
I will make the required changes in the program, thanks for reporting

ilko_t, thanks for your reply.

I tried what you suggested, both copying the setup.ex_ file from my source and changing SET TAG= to \OEM, but I still do not get driverpacks extraction at the beginning of setup nor are any of the contents of the $OEM$ folder copied over. I tried creating a fresh USB stick then changing SET TAG= to \OEM but this also did not yield any results.

Edit: Apologies for my lack of reading ability, did not notice the bit about copying WIN51 to the root of the USB. DriverPacks is now extracting correctly at setup.

Just out of interest, what does the WIN51 file do? I had a look at it with Notepad and it only seems to contain the word "Windows"!

Having said that, changing the set tag to SET TAG=\OEM in presetup.cmd did not seem to have any effect.

This post has been edited by Xeijin: 24 February 2009 - 09:04 AM

[ilko_t]

It seems presetup.cmd does not get executed. The reason would be incorrect setup.ex_ used.
Can you put back \files\winsetup\setup.ex_ in ~LS\I386 AND change SET TAG= to \OEM.
If that resolves the problem, compare the extracted setup.ex_ (expand setup.ex_ setup.exe) with setupORG.exe in your XP source, are they the same? If yes- what BTS base did you use, any night build or beta? Have you used nLite or similar tool AFTER integrating BTS packs? Just random ideas...
BTW- do you have any internal/external card readers in this computer? Can you disconnect or disable them?

This post has been edited by ilko_t: 24 February 2009 - 08:50 AM

[ilko_t]

jaclaz, on Feb 24 2009, 01:47 AM, said:

Just for the record...

[Xeijin]

Have edited my original post ilko_t, it is now working fine, I forgot to copy the WIN51 file as you suggested. Thanks again for all the support!

[ilko_t]

I am glad it's now resolved
The file is just a tag file, it should have worked with any other TAG file or folder, which is present on the USB, e.g. SET TAG=\$WIN_NT$.~BT, unless that tag is coded in the fake setup.ex_ as well. Have to play a bit with the latest BTS packs to see what has been changed.