[ilko_t]

Did you move the radio button fixed/removable?

You may also try the latest beta, which works in a slightly different manner:
http://www.datafileh...d-20d0545c.html

[kof94]

Welll my first attempt ended with a code 18 error about missing biosinfo,inf, which *is* on the UFD.

I'm gonna give it another go but I have one question... is the migrate.inf really required? The reason I ask is, I create backups of my disk using dd (there's a lot of other stuff on it), if I write my image to a new disk (if say my current disk dies) will it still work?

[kof94]

Second go, same thing:

File \WIN_SETUP\XP_Pro_SP3\I386\biosinfo.inf could not be loaded
The error code is 18

...

The file exists... any ideas?

Edit: Nevermind, I renamed the directories \WINSETUP\XP\ and everything works.

This post has been edited by kof94: 18 December 2009 - 02:15 PM

[ilko_t]

Well done, thanks for reporting

Next is Jaclaz to pull my ears for not using 8.3 filenames

More interesting is why it matters in your setup, what file system was this USB disk formatted in?

[Arvi]

It didn't help. Now I installed WinSetupFromUSB to default place (with 8.3 filename). I made new USB and start first boot but error is same. My USB filesystem is NTFS. I attach new log file.

Attached File(s)

•  WinSetupFromUSB.zip (64.57K)
  Number of downloads: 8

[ilko_t]

The log file is from 0.2.3, not from the beta version I gave you link to, did you try it at all? I do have something in mind to point you to that version.

What partition are you installing on? Was it created in advance? Using what tool? Under what operating system? Describe your partitions with their sizes and file systems too.

Can you attach these files from your source- D:\I386\TXTSETUP.OEM and WINNT.SIF, in the latter remove any sensible information such as serial number etc.

[kof94]

ilko_t, on Dec 19 2009, 04:27 AM, said:

Well done, thanks for reporting

Next is Jaclaz to pull my ears for not using 8.3 filenames

More interesting is why it matters in your setup, what file system was this USB disk formatted in?

To be honest so many things could be different with my setup.

My main OS is Slackware, I used fdisk (coreutils) to create a FAT32 (LBA) partition and mkdosfs to create a FAT32 filesystem on my disk then ran your GUI inside VirtualBox to do the rest.

It's an odd arrangement I will admit but it works for me.

Edit: I nearly forgot... The feature I'd most like to see is an option that just creates the ISO without doing the file copying. I can copy/move setup.cmd and setup(org).exe myself!
I also did a test removing migrate.inf... it made no difference.

@Arvi
I had to edit setup.cmd and txtsetup.sif (inside the ISO) to get this to work... I don't know if this helps.

This post has been edited by kof94: 19 December 2009 - 04:15 AM

[Arvi]

I tested now with beeta.
With beeta: I formated my USB with RMPrepUSB. This make USB two partitions: first is NTFS main parttions and second is unactive unknown with capacity 0MB. After boot I got error message:
root (hd0,F:)
Error 11: urecognized device string, or you omitted the required device part which should lead the filename.
I attach log.

With 0_2_3: I formatted with RMPrepUSB NTFS format. This make USB two partitions: first is NTFS 3.8GB parttions and second is unactive unknown with capacity 0MB. I deleted both partitions but RMPrepUSB make two partitions. I tried to install on USB 3.8GB partition not 0B partition. In my computer is winXP pro.

Attached File(s)

•  WinSetupFromUSB.zip (64.57K)
  Number of downloads: 8
•  WINNT.SIF (107bytes)
  Number of downloads: 2
•  TXTSETUP.zip (1.79K)
  Number of downloads: 3

[Arvi]

I think that problem is not with Dell winXP CD. Before I wrote here first time I tested USB install with original Microsoft XP Pro CD also. Issue was same.

[kof94]

Arvi, on Dec 19 2009, 01:06 PM, said:

I tested now with beeta.
With beeta: I formated my USB with RMPrepUSB. This make USB two partitions: first is NTFS main parttions and second is unactive unknown with capacity 0MB. After boot I got error message:
root (hd0,F:)
Error 11: urecognized device string, or you omitted the required device part which should lead the filename.
I attach log.

With 0_2_3: I formatted with RMPrepUSB NTFS format. This make USB two partitions: first is NTFS 3.8GB parttions and second is unactive unknown with capacity 0MB. I deleted both partitions but RMPrepUSB make two partitions. I tried to install on USB 3.8GB partition not 0B partition. In my computer is winXP pro.

At the bottom of menu.lst or winsetup.lst (I can't remember) change the line that reads root (hd0,F:) to root (hd0,0) or even better find --set-root /winsetup.lst. This should solve your problem.

Edit: Here's some files for you. txtsetup.sif (for ISO), setup.cmd, menu.lst and winsetup.lst

Attached File(s)

•  files.7z (69.06K)
  Number of downloads: 13

This post has been edited by kof94: 19 December 2009 - 08:56 AM

[Arvi]

kof94, on Dec 19 2009, 04:36 PM, said:

Arvi, on Dec 19 2009, 01:06 PM, said:

I tested now with beeta.
With beeta: I formated my USB with RMPrepUSB. This make USB two partitions: first is NTFS main parttions and second is unactive unknown with capacity 0MB. After boot I got error message:
root (hd0,F:)
Error 11: urecognized device string, or you omitted the required device part which should lead the filename.
I attach log.

With 0_2_3: I formatted with RMPrepUSB NTFS format. This make USB two partitions: first is NTFS 3.8GB parttions and second is unactive unknown with capacity 0MB. I deleted both partitions but RMPrepUSB make two partitions. I tried to install on USB 3.8GB partition not 0B partition. In my computer is winXP pro.

At the bottom of menu.lst or winsetup.lst (I can't remember) change the line that reads root (hd0,F:) to root (hd0,0) or even better find --set-root /winsetup.lst. This should solve your problem.

Edit: Here's some files for you. txtsetup.sif (for ISO), setup.cmd, menu.lst and winsetup.lst

I replaced root (hd0,F:) with root (hd0,0) in menu.lst. Now wasn't errors. I selected first installation part. But it wants to install OS to my HDD. He asked do I want repair or reinstall my C: disk OS. Now was not possible select on which partition I want install.

[kof94]

If you hit Enter you should be able to delete/create a new partition on your HDD and install Windows.

Setup wont allow you to delete the partition on your UFD.

If the wrong drive letter is assigned (e.g. your HDD has no partition(s) to start with) then setup.cmd will force a reboot and reset the drive letter to C: at first GUI.

I hope this makes sense because I'm a little confused with what your trying to do... do you want to install Windows on your HDD from your UFD?

[kof94]

Something else I've just discovered... $OEM$ dir works. I don't know why I thought it wouldn't but my cmdlines.txt is ran at T-13.

The only draw back is the drive letter for the UFD changes after second reboot so any paths set at T-13 for RunOnceEx are incorrect when you get to the desktop.

This isn't an issue though as I can work around it. Infact I could just launch the same script via GUIRunOnce instead and make the $OEM$ dir redundant

[berry tsakala]

I had an HAL.DLL error, and solved it.

i'm not sure it's WinSetupFromUSB's fault,
but in case it will be helpful to other users, and in case you can actually prevent it in the future, i'm posting my case here

here are the details:

my question (and my answer) on "server fault.com"

here's my log file (i had 3 log files, and i don't know which is relevant, but it doesn't seem to matter in my case)

thanks for the program. it works, and it helped!

Attached File(s)

•  20091218_071856_log.cab (476bytes)
  Number of downloads: 1

[jaclaz]

berry tsakala, on Dec 20 2009, 01:43 AM, said:

I had an HAL.DLL error, and solved it.

Maybe you missed that the FAQ's:
http://www.msfn.org/...qs-t116766.html

try to address common problems, and #4 seems like the one you reported .

I find much more "preoccupying" the other two issue you reported:

• D: as drive letter
  
• Setup files deleted

Can you post some more exact details of what you did and which options you chose (and also which version did you use)

jaclaz

[Mihail_]

it is possible to make install-USB_HDD with three operating systems (XP, Vista, 7) that the files from each placed in a different folders?

for example, files from WinXP.ISO in the directory "WINXP", files from 7 - in "WIN7", etc..?

Thanks for help!

This post has been edited by Mihail_: 20 December 2009 - 03:04 PM

[garishakhoyan]

great job

[ilko_t]

kof94, on Dec 19 2009, 01:19 PM, said:

...The only draw back is the drive letter for the UFD changes after second reboot so any paths set at T-13 for RunOnceEx are incorrect when you get to the desktop.

Changes from which to which? Which one is the "second reboot", the GUI mode, or after it?

Mihail_, on Dec 20 2009, 01:04 PM, said:

it is possible to make install-USB_HDD with three operating systems (XP, Vista, 7) that the files from each placed in a different folders?

for example, files from WinXP.ISO in the directory "WINXP", files from 7 - in "WIN7", etc..?

You can place any versions of 2000/XP/2003 in the same partition, as many as you want using the beta WinSetupFromUSB (don't go beyond 99 thought ), and one of the Vista/7/server 2008 into the same partition. The other Vista/7/2008 must go in a separate partition, which should not be a problem since you are using USB hard disk. Vista and above cannot go into own folder, unless you launch first some type of Vista/7 PE, and start setup from cmd line executing setup.exe from the folder you placed the setup files.
Have a look in the subforum, this has been discussed numerous times. At first page of this topic is also mentioned what's supported and what's not.

garishakhoyan, on Dec 21 2009, 12:08 AM, said:

great job

Thanks

In other hand- call for community participation- only for a few hours since beta2 was posted it was downloaded over 1000 times, and not a single feedback so far. I can hardly release a stable version without some help with testing and feedback, no matter if there were issues or not.
Guys, come on, give a hand

[kof94]

Quote

Changes from which to which? Which one is the "second reboot", the GUI mode, or after it?

At T-13 the UFD is still seen as D: but after the second reboot (after oobe, when RunOnceEx is started) it is seen as H: (I have card readers and other disks). It's no problem though I've just switched to using GUIRunOnce instead.

Quote

In other hand- call for community participation- only for a few hours since beta2 was posted it was downloaded over 1000 times, and not a single feedback so far. I can hardly release a stable version without some help with testing and feedback, no matter if there were issues or not.
Guys, come on, give a hand smile.gif

Whats new, did you considered this:

Quote

...
Edit: I nearly forgot... The feature I'd most like to see is an option that just creates the ISO without doing the file copying. I can copy/move setup.cmd and setup(org).exe myself!
I also did a test removing migrate.inf... it made no difference.
...

Also, would you consider changing this:

setup.cmd

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

to this:

set TAGFILE=\WINSETUP
for /f "tokens=1 delims=: " %%? in ('mountvol.exe ^|find ":\"') do (
  dir %%?:%TAGFILE% > nul 2>&1 && set CDDRIVE=%%?:
)
if defined CDDRIVE goto :CDDRIVE_found

Stops "no disk" errors for us poor fools with card readers!

[ilko_t]

kof94, on Dec 21 2009, 02:28 PM, said:

Quote

In other hand- call for community participation- only for a few hours since beta2 was posted it was downloaded over 1000 times, and not a single feedback so far. I can hardly release a stable version without some help with testing and feedback, no matter if there were issues or not.
Guys, come on, give a hand smile.gif

Whats new, did you considered this:

Quote

...
Edit: I nearly forgot... The feature I'd most like to see is an option that just creates the ISO without doing the file copying. I can copy/move setup.cmd and setup(org).exe myself!
I also did a test removing migrate.inf... it made no difference.
...

This would require significant change in code, plus there are a few changes in the source folder- winnt.sif and fake setup.exe. Wouldn't do it unless there is enough interest in implementing it.

A lot of stuff is new, menu.lst creation is fixed, using short file names, excessive logging etc. Besides, there were just a couple of spartan reports for the previous beta
As for what's new from 0.2.3- the whole method of installing:
http://www.msfn.org/.../2-t139737.html

kof94, on Dec 21 2009, 02:28 PM, said:

Also, would you consider changing this:

setup.cmd

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

to this:

set TAGFILE=\WINSETUP
for /f "tokens=1 delims=: " %%? in ('mountvol.exe ^|find ":\"') do (
  dir %%?:%TAGFILE% > nul 2>&1 && set CDDRIVE=%%?:
)
if defined CDDRIVE goto :CDDRIVE_found

Stops "no disk" errors for us poor fools with card readers!

Sure, it's actually in the to-test list