[NikLok]

ilko_t, on 08 April 2011 - 08:50 PM, said:

Why? Anything wrong with latest or any new features you need?

I wait sourse code very long time!
I dream add abbility rewrite only new files to the flash!
I intagrate ms updates every mounth, because i need have distributive with latest updates!
I install 5-10 system every mounth.

Now when i use subj he make new copy of contents ( XppSp3 XppSp31 XppSp3.iso XppSp31.iso ......)
But realy changed very small quontity files!

You dont want make this feature.
I try to do this self.

This post has been edited by NikLok: 11 April 2011 - 04:42 AM

[Flashmann]

@ilko_t

ilko_t, on 10 April 2011 - 10:31 AM, said:

@Flashmann

Does it work in QEMU? Run the program with the USB HD attached and select only "test in QEMU". Does it load?

On real hardware- try renaming on the USB HD \WINSETUP\XP..sp3\I386\migrate.inf to migrate.inf.bak. Does it load?

QEMU doesn't work at all, seems to me. I checked "Test in QEMU", then "GO" button. Nothing appears in next 5~7 seconds, and then it says "Job done".

Renaming migrate.inf has caused BSOD, image attached.

Attached File(s)

•  ABCD0014.jpg (184.15K)
  Number of downloads: 23

[cdob]

Flashmann, on 10 April 2011 - 08:38 AM, said:

Weird, but stick works fine, except USB HDD.

Which USB HDD do oyu use?
Which storgage capacity goes to hard disk?
Do you use several partitions?

BIOS routines are used to read files at textmode part.
Some BIOS limit access to first part only, example first 128GB only.

[Flashmann]

cdob, on 11 April 2011 - 09:17 AM, said:

Which USB HDD do oyu use?
Which storgage capacity goes to hard disk?
Do you use several partitions?

BIOS routines are used to read files at textmode part.
Some BIOS limit access to first part only, example first 128GB only.

Seagate FreeAgent Go 500 Gb, first partition is 15,8 Gb (which is used for setup files) and second is 450 Gb for my files.

[ilko_t]

Flashmann, on 11 April 2011 - 06:55 AM, said:

QEMU doesn't work at all, seems to me. I checked "Test in QEMU", then "GO" button. Nothing appears in next 5~7 seconds, and then it says "Job done".

This is weird. What did you use to extract WinSetupFromUSB.7z ? Use 7-zip from 7-zip.org some other programs tend to incorrectly extract 7z archives. What Windows version do you use?

Flashmann, on 11 April 2011 - 06:55 AM, said:

Renaming migrate.inf has caused BSOD, image attached.

That's even weirder. Migrate.inf should not be cause for BSOD. MS article suggests:

Quote

The ACPI Bios in this system is not fully compliant to the specification

http://support.microsoft.com/kb/314830

Try hitting F7 when F2/F6 prompt appears as the article suggests, does it load to the partitioning screen?
Can you update BIOS?
Can you load BIOS defaults?
Does USB HD prepared by 0.2.3 version work?

Have you tried it on another hardware?

[Joshatdot]

ilko_t, on 07 April 2011 - 05:49 PM, said:

@Joshatdot

I don't get the point and can't make sense of these reports, thanks for sharing, but is there some conclusion?
NTFS on 0.x.x. versions is ways faster, have a look:
http://www.msfn.org/...d-on-usb-stick/

On 1.x versions file system should not matter that much, except when preparing the stick.

The difference between both versions is that in method used in 0.x.x versions Setup attempts to delete the files as they are copied, due to NTFS cache speed is much faster, in XP and 2003.

In 1.X versions another method is used and files are not attempted to be deleted, hence NTFS does not improve speed during file copy stage in Text mode.
As for the loading part up to the "Setup is starting" I really doubt there is significant difference in speeds, plus it should not be that important whether Setup starts for 20 or 40 seconds, not a big deal.

Conclusion, using 0.23 with NTFS works best for me, at least on the HP mini 110-1012NR I was working on. When I prep'ed my stick with 1.07b it took at least 20x slower just loading Setup .. regardless of FAT or NTFS format. I should have made a video to show how slow it was. The time it took, with 1.07b, to inspect the hardware & loading Setup (before the HDD drivers were loading) .. that same stick prep'd with 0.23 was already done loading & asking me to press F8 to accept EULA.

[Pulento]

Hello everyone

I have some problems installing Windows XP with WinSetupFromUSB.

1. I downloaded and installed WinSetupFromUSB in C:\WinSetupFromUSB (0.2.3 version).
2. My PC has installed Windows 7 64.
3. I create the folder C:\WINXPCD and copied all files from the Windows XP Setup CD.
4. I used a Kignston USB stick 1GB.
5. I formated the pendrive using the RMPREPUSB 1.975.
6. Then I run the program and finished without problems.


The destination machine was a notebook, Acer Aspire 1640.
With a new HD (formated) Samsung IDE, 160GB, model HM160HC.

After install the first part of Windows XP, with no issues, I tried to install the second part but I got the next message:

------------------------

Windows could not start because of a computer disk hardware configuration problem.

Could not read from the selected boot disk. Check boot path and disk hardware.

Please check the Windows documentation about hardware disk configuration and your hardware reference manuals for additional information.

------------------------



I would like to show you the process using images, so maybe you can find and issue during the installation:














































After the error, I took of the HD and sticked it on my PC and this is the list of the files on it:




I did the process almost 8 times. I used 3 different pendrives but I got the same error message.

I will apreciate if anyone of you could help me to fix this.

Thanks in advance

Alvaro

This post has been edited by Pulento: 19 April 2011 - 08:34 AM

[nothingspecial]

It works like charm...thanks

[ilko_t]

@Pulento

Did you try the debug entries below, HD1 part 1 etc., on the screen with black background?

I'd also use the latest version, currently 1.0 beta7.

[Pulento]

ilko_t, on 20 April 2011 - 10:09 AM, said:

@Pulento

Did you try the debug entries below, HD1 part 1 etc., on the screen with black background?

I'd also use the latest version, currently 1.0 beta7.

Hey ilko_t

Thanks for your reply.

Yes, I tried all, but no ones work.

Ok, I will try the latest version (1.0 beta7) right away.

I will back with news.

Thanks again

Alvaro

[Pulento]

Hi ilko_t

Ok, I tried the 1.0 beta7.

It didn't work.
Sorry.

I run the program, and did the format just the way it was on the window:




But near to the end I got the next error message:



Sorry, part of the information is in portuguese.
I repeat the process and I got the same error again.



But after the error seems the instalation ends fine:





Well, hoping that error wasnt a big deal I tried again.
Here are the pictures of the process:











And then I got this error:

PCI System Error on Bus/Device/Function 0000h





Then, I tried again, but this time I choose the PLoP boot manager:




I choose HDD PARTITION 1




But I got this error:




I did the process again but this time I tried chosing the pendrive, I got this:




BOOTMGR is missing
Press trl+Alt+Del to restart



By the way, there is a diference between the pendrive content for each version of


0.2.3:





1.0 beta7:





I dont know if this have to do with it. Im not the expert here



Well, hope you can give me a hand to solve this.

Thanks again for your time. I really apreciate it.

Muito obrigado


Alvaro

[ilko_t]

Sorry, I am out of town for a few weeks with limited access to internet. Will have a look when come back first days of May if you have not figured it out.

[BzowK]

Good Morning -

I've been using WinSetupForUSB for a while now and love it! It's the only app that I've ever been able to find that does just what I need it to do. Currently, I have a 64g USB/eSATA Kanguru drive with multiple WIndows installations, Linux Dists, and utility discs.

Here's my issue: I use SCCM to deploy operating systems (OSD) at my work. To do this (since I don't have PXE), a 150 mb boot disc is used which is basically Windows PE. I have 4 major discs that I use for two different distribution points and the x86 and x64 versions of each. I also frequently use a different Windows PE image to copy WIM files from images.

I tried to add each of these images with WinSetupFromUSB by extracting each to different folders, then adding them under the Windows7/PE section. The problem is that when I went to edit each of their titles in the menu.lst, I was that each of the 5 images I imported had the exact same entry (below)

title Start Windows PE x86
map --unmap=0:0xff
map --unhook
root (hd0,0)
chainloader /bootmgr

I also tried adding the ISO itself under the Linux ISO section. It copied successfully to by USB drive. When I booted to the menu and loaded it, I was surprised to see that it actually started loading Windows PE, but gave error messages soon after it loaded the GUI.

Does anyone have any suggestions to how I can get all 5 different images onto one drive?

Thanks!

[jaclaz]

Check FIRST post of this thread.
Particularly this part :

Quote

- Vista/Windows 7/Server 2008 setup to different primary partitions. Multiple Vista sources in the SAME partition are NOT supported. Place your second Vista/7/Server 2008 setup in another partition. It can be placed in any primary partition. If looking for several Vista/Server 2008/7 sources in the same partition have a look here or if just for 7 or Vista here. The first ling would require you manually to put everything to the USB disk, if using the second you can point the program to the prepared AOI source.

I presume you want to follow this approach:
http://sites.google....site/rmprepusb/
http://sites.google....and-server-2008
or this:
http://sites.google....utorials/winiso
or this:
http://sites.google....iskautounattend

(or something "in between").

jaclaz

[BzowK]

Great - Thanks for the thorough reply. It's exactly the information that I needed - Thanks Again

[ilko_t]

@Pulento

How far did you get, any updates?

[kadetov1]

Hi! I need some migrate utility for changing a drive letter to U: of my USB stick! I want to change manual a drive letter to U: of the USB stick under Windows 7. I tried to do it by MkmigrateInf3.cmd, but when I start installing XP, drive letter is D: Anybody can help me?

This post has been edited by kadetov1: 11 May 2011 - 02:28 PM

[ilko_t]

If I got the question right you don't need any external program, just use the built-in disk management and drive letter reassignment.
If you have something else in mind please clarify.

[kadetov1]

I use WinSetupFromUSB 1.0 beta 7 for creating USB stick with XP os. It assigned me U: drive letter, all right. But I want to assign a drive letter manual (under Windows 7) without using WinSetupFromUSB 1.0 beta 7, such as MkmigrateInf3.cmd . Example: I just copied all files that created WinSetupFromUSB 1.0 beta 7 to another USB flash (install grub, etc), but when I boot from this flash it doesn't assign U: drive letter. And I want to assign a drive letter manual without built-in disk management. What is the program in WinSetupFromUSB 1.0 beta 7 package that assignes U: drive letter? How do it? And where can I get lastest version of MkMigrateInf.cmd that works perfect under Windows 7?
How to creat it manual (assign U: drive letter) such as do it WinSetupFromUSB (under Windows 7):

[Version]
Signature = "$Windows NT$"

[Addreg]
HKLM,"SYSTEM\MountedDevices",,0x00000010
HKLM,"SYSTEM\MountedDevices","\DosDevices\U:",0x00030001,\
5C,00,3F,00,3F,00,5C,00,53,00,54,00,4F,00,52,00,41,00,47,00,45,00,23,00,52,00,65,00,6D,00,6F,00,76,00,61,00,62,00,6C,00,65,00,4D,00,65,00,64,00,69,00,61,00,23,00,37,00,26,00,31,00,38,00,30,00,63,00,38,00,34,00,65,00,38,00,26,00,30,00,26,00,52,00,4D,00,23,00,7B,00,35,00,33,00,66,00,35,00,36,00,33,00,30,00,64,00,2D,00,62,00,36,00,62,00,66,00,2D,00,31,00,31,00,64,00,30,00,2D,00,39,00,34,00,66,00,32,00,2D,00,30,00,30,00,61,00,30,00,63,00,39,00,31,00,65,00,66,00,62,00,38,00,62,00,7D,00

HKLM,"SYSTEM\MountedDevices","\DosDevices\V:",0x00030001,\
5C,00,3F,00,3F,00,5C,00,53,00,54,00,4F,00,52,00,41,00,47,00,45,00,23,00,52,00,65,00,6D,00,6F,00,76,00,61,00,62,00,6C,00,65,00,4D,00,65,00,64,00,69,00,61,00,23,00,36,00,26,00,31,00,38,00,30,00,63,00,38,00,34,00,65,00,38,00,26,00,30,00,26,00,52,00,4D,00,23,00,7B,00,35,00,33,00,66,00,35,00,36,00,33,00,30,00,64,00,2D,00,62,00,36,00,62,00,66,00,2D,00,31,00,31,00,64,00,30,00,2D,00,39,00,34,00,66,00,32,00,2D,00,30,00,30,00,61,00,30,00,63,00,39,00,31,00,65,00,66,00,62,00,38,00,62,00,7D,00

HKLM,"SYSTEM\MountedDevices","\DosDevices\W:",0x00030001,\
5C,00,3F,00,3F,00,5C,00,53,00,54,00,4F,00,52,00,41,00,47,00,45,00,23,00,52,00,65,00,6D,00,6F,00,76,00,61,00,62,00,6C,00,65,00,4D,00,65,00,64,00,69,00,61,00,23,00,38,00,26,00,31,00,38,00,30,00,63,00,38,00,34,00,65,00,38,00,26,00,30,00,26,00,52,00,4D,00,23,00,7B,00,35,00,33,00,66,00,35,00,36,00,33,00,30,00,64,00,2D,00,62,00,36,00,62,00,66,00,2D,00,31,00,31,00,64,00,30,00,2D,00,39,00,34,00,66,00,32,00,2D,00,30,00,30,00,61,00,30,00,63,00,39,00,31,00,65,00,66,00,62,00,38,00,62,00,7D,00

This post has been edited by kadetov1: 12 May 2011 - 08:05 AM

[ilko_t]

Windows Vista and above calculate MountedDevices keys for removable drives in a different way. MkMigrateInf does not work with them. The algorithm calculating the needed values is built in the latest versions of the program, no external program is used.