[cdob]

davlak, on 17 February 2011 - 01:32 PM, said:

after reboot I needed to build the MBR before step 2.

Setup writes MBR to hd0.

You may have to adjust the mapping:
map (hd0) (hd1)
map (hd1) (hd0)

Overall there seems to be a BIOS, USB, windows and winvblock confusion.
I consider this experimental still.

@all
Which hardware and windows do you use?

[tonyzg]

OK, here's what I've managed to do so far.
With RMPREPUSB I wasnt able to produce USB that can boot on all my PCs.
On newer machines I was getting blinking cursor.
At the end I formated the USB through Windows format to NTFS and tha installed
grub4dos through RMPREPUSB and clicked NO when installation asked do I
want to install it to MBR so it installed to PBR instead.

Other USB I made with Make_USB and left "Standard" MBR BootCode install option on.

Both USB sticks now boot on all PCs I've tested so far (except that workstation W6000)
and the Windows installation pass the point where I got blue screen before, but when I press
ENTER to select where I want to install Windows I'm only getting partition C: and that
is my USB stick.

menu.lst is the one wimb suggested. Do I have to change mapping in menu.lst?
I'm guessing that device (USB) was probably not made as it should be but maybe
some other type of mapping could solve this. I'll leave that to experts...

@ cdob

I'm on Windows XP SP3 Professional. What info about the hardware do you need?
Type of motherboard, BIOS, RAM...?

[wimb]

tonyzg, on 18 February 2011 - 07:19 AM, said:

but when I press
ENTER to select where I want to install Windows I'm only getting partition C: and that
is my USB stick.

You are missing MassStorage driver needed to see your Harddisk.

http://driverpacks.net/downloads
For Install of XP on a modern system with SATA Drives it is needed to use DPsBase.exe
for Integrating in your XPSOURCE BTS DriverPack Massstorage with TXT Mode Enabled.

[tonyzg]

wimb, on 18 February 2011 - 07:59 AM, said:

You are missing MassStorage driver needed to see your Harddisk.

http://driverpacks.net/downloads
For Install of XP on a modern system with SATA Drives it is needed to use DPsBase.exe
for Integrating in your XPSOURCE BTS DriverPack Massstorage with TXT Mode Enabled.

That is probably right because on older PC with IDE disk that I tested 30 minutes ago everithing was OK.
I have mass storage driver integrated in my iso file from the start.
I downloaded "DriverPack Mass Storage 11.01 for Windows 2000/XP/2003 (x86)" and integrated them
with my source, but with nLite. Does it realy have to be made with DPsBase.exe? If it have to be it
do I use method 1 or method 2 of slipstreaming?

Another thing I noticed when I try to install on a newer machine is that I didn't see winvblock drivers
loading at starting point of Windows installation. I remember that few times on older USB setup I noticed
that winvblock drivers are indeed loading. Could it be that my bootable USB wasn't made the
right way? I'll try to test some more after I get answers to upper questions.

This post has been edited by tonyzg: 18 February 2011 - 08:57 AM

[wimb]

tonyzg, on 18 February 2011 - 08:44 AM, said:

Does it realy have to be made with DPsBase.exe? If it have to be it
do I use method 1 or method 2 of slipstreaming?

You need the MassSorage as boot driver.
I would advise to use DPsBase.exe and MassStorage + TXT-mode enabled (gives boot driver)
and use method 2 (as always).

@cdob
I am using AMD Athlon 64 X2 Dual Core 4800+ and ASUS M2A-VM HDMI mobo
and Windows XP SP3 Professional (with and without UpdatePack)
I found that if the WinVBlock virtual floppy is defined in RAM using --mem option,
then the virtual CD on USB will survive install of devices in GUI mode and XP Setup is OK.
Without --mem for virtual floppy then the virtual CD on USB is lost just after install of devices in GUI mode and XP Setup will FAIL.

This post has been edited by wimb: 18 February 2011 - 10:03 AM

[Doodoo]

davlak, on 17 February 2011 - 01:32 PM, said:

as usual no way to repair the unknown device (winvblock) in device manager into XP.

If you look carrefully, I think the device is working absolutely fine, there is no exclamation mark on the device icon.
It is just an unknown device, and it comes with a question mark; XP does not know in which correct category it should put it (SCSI and RAID controllers). But it is really working fine and does not need repairing.

[cdob]

wimb, on 18 February 2011 - 09:35 AM, said:

I am using AMD Athlon 64 X2 Dual Core 4800+ and ASUS M2A-VM HDMI mobo
and Windows XP SP3 Professional (with and without UpdatePack)
I found that if the WinVBlock virtual floppy is defined in RAM using --mem option,
then the virtual CD on USB will survive install of devices in GUI mode and XP Setup is OK.

At a ASrock N68C-S UCC (AMIBIOS) map --mem fails still. CD-ROM disappear at PNP.

Idea: Open a handle to virtual CD-ROM drive.
Compare http://www.msfn.org/...post__p__954022

Press shift F10 to open command console at a default install ISO.
Change directory to virtual CD ROM drive.
This opens a handle CD ROM drive. Keep this windows open. PNP dosn't truncate access.

At DriverPacks edit presetup.cmd

:DPsFound
start /b "Open handle to virtual CD-ROM drive." pushd "%CDDRIVE%"

Another cmd.exe is launched in context to running hidden presetup.cmd.
Hence this cmd.exe is hidden too.

At driver February 14 I don't use virtual floppy at first reboot anymore.
Driver and txtsetup.oem was updated. Add file winvblk.cat to virtual floppy too.

Quote

title 2 Continue Windows XP setup
map /Inst/XP_RAM.ISO (0xff)
checkrange 0x80 read 0x8280 && map (hd0) (hd1) && map (hd1) (hd0)
map --hook
chainloader (hd0)+1

[tonyzg]

wimb, on 18 February 2011 - 09:35 AM, said:

You need the MassSorage as boot driver.
I would advise to use DPsBase.exe and MassStorage + TXT-mode enabled (gives boot driver)
and use method 2 (as always).

Thanks, that worked just fine and I passed the point of blue screen now on newer machines.
I didn't tried to finish the installation on that PC thou.

I'll try on older PC today at work... (I reedited my post if you saw it few minutes ago because
I have to try it again... I made mistake in menu.lst)

This post has been edited by tonyzg: 22 February 2011 - 12:38 AM

[steve6375]

I had similar issue to Wimb. See my tutorial on RMprepUSB website at http://sites.google....-xp-from-an-iso

Step 1 works fine when directly mapped to the ISO
Step 2 GUI stage crashes unless iso is mapped using --mem :-(


@tonyzg - re. RMPrepUSb and flashing cursor. Did you try latest version of RMPrepUSB = v2.1.617. This should be fixed. If not can you send me the contents of the MBR of your working USB drive as it seems that the systems that give a flashing cursor do not like the RMPrepUSB MBR??? The latest version has a modified version of grub4dos too so you can install to MBR or PBR. I would be interested to know if they both worked on all your systems?

[Doodoo]

steve6375, on 23 February 2011 - 06:10 PM, said:

Step 1 works fine when directly mapped to the ISO
Step 2 GUI stage crashes unless iso is mapped using --mem :-(

Have you tried cdob's trick ?
Presumably this applies to a vanilla XP ISO:

cdob, on 21 February 2011 - 04:14 PM, said:

Press shift F10 to open command console at a default install ISO.
Change directory to virtual CD ROM drive.
This opens a handle CD ROM drive. Keep this windows open. PNP dosn't truncate access.

and this to a modified ISO with DriverPacks integrated:

cdob, on 21 February 2011 - 04:14 PM, said:

At DriverPacks edit presetup.cmd

:DPsFound
start /b "Open handle to virtual CD-ROM drive." pushd "%CDDRIVE%"

Another cmd.exe is launched in context to running hidden presetup.cmd.
Hence this cmd.exe is hidden too.

It would be very useful to know if this trick solves the problem in your case.

[wimb]

cdob, on 21 February 2011 - 04:14 PM, said:

At DriverPacks edit presetup.cmd

:DPsFound
start /b "Open handle to virtual CD-ROM drive." pushd "%CDDRIVE%"

Another cmd.exe is launched in context to running hidden presetup.cmd.
Hence this cmd.exe is hidden too.

This modification of presetup.cmd works for me.
The WinVBlock virtual floppy is NOT needed anymore at reboot for GUI-mode.
The XP Setup source in virtual CD on USB is found and survives install of devices.
GUI-mode of XP Setup continues without error. Install of XP is OK.

The proposed title 2 of grub4dos menu did NOT work for me.
On selecting title 2 I returned to grub4dos menu on USB-stick.

I did modify and used original mapping of title 2 and then everything worked for me:

title 1 Start Windows XP setup - XP3_11_2.iso
map --mem /winvblock.ima (fd0)
map --mem /winvblock.ima (fd1)
map /XP3_11_2.iso (0xff)
checkrange 0x80 read 0x8280 && map (hd0) (hd1)
checkrange 0x80 read 0x8280 && map (hd1) (hd0)
map --hook
chainloader (0xff)
 
title 2 Continue Windows XP setup
map /XP3_11_2.iso (0xff)
checkrange 0x80 read 0x8280 && map (hd0) (hd1)
checkrange 0x80 read 0x8280 && map (hd1) (hd0)
map --hook
chainloader (hd0)+1

Boot twice from USB (using title 1 and 2) - and then Reboot from drive where XP is installed.
Congratulations with the NEW method for Install of XP from USB
I think it is the most simple way to Install XP from USB

The same method can also be used to Install XP in HDD Image file
as described by Doodoo and sara - pmedia and wimb
http://reboot.pro/13...385#entry122385
http://reboot.pro/13731/
http://www.911cd.net...showtopic=23553

Attached File(s)

•  CDOB_CD_USB.png (84.65K)
  Number of downloads: 84

This post has been edited by wimb: 25 February 2011 - 09:18 AM

[Doodoo]

wimb, on 25 February 2011 - 12:46 AM, said:

The WinVBlock virtual floppy at reboot for GUI-mode is NOT needed anymore.

Except maybe if you want to use an answer file ? Or do you include it in the ISO itself (but I find that a little less flexible... Just a matter of personal taste really)

[wimb]

Doodoo, on 25 February 2011 - 02:43 AM, said:

Except maybe if you want to use an answer file ?

The winnt.sif file is only needed in TXT-mode.

The GUI-mode will use the created WINDOWS\system32\$winnt$.inf file which contains the info of winnt.sif

This post has been edited by wimb: 25 February 2011 - 04:16 AM

[jaclaz]

Topic pinned.

jaclaz

[karyonix]

If you tell ISO file name to WinVBlock in step 2, it should keep ISO file opened without having to use cmd trick.
Or you may try FiraDisk 0.0.1.30 with ISO file name in its parameter in small mem drive.

This post has been edited by karyonix: 28 February 2011 - 01:02 PM

[steve6375]

Quote

I've tested it and works, setup goes on in text mode but after reboot I needed to build the MBR before step 2.
But I seriously suppose there must be a bug into the bios of my old test machine (mobo foxconn cpu intel p4).
as usual no way to repair the unknown device (winvblock) in device manager into XP.

@Davlak
Did you delete the partitions and reformat using XP Setup or did you leave the existing partition and just reformat. If you have off-track partitions (such as made by WinPE v2 and v3 DISKPART) then it may well fail to boot from HDD.
Always create a new partition for your tests.
I have to use DISKPART with the CRE PRI ALIGN 1065 command in WinPE v2/v3 before running winnt32 to ensure the partition is on a cylinder boundary. It may be the same with Setup?

This post has been edited by steve6375: 28 February 2011 - 01:44 PM

[wimb]

karyonix, on 28 February 2011 - 01:01 PM, said:

If you tell ISO file name to WinVBlock in step 2, it should keep ISO file opened without having to use cmd trick.
Or you may try FiraDisk 0.0.1.30 with ISO file name in its parameter in small mem drive.

I tried to tell ISO filename to WinVBlock in step 2,
but unfortunately the virtual CD drive on USB-stick did NOT survive Install of devices in GUI-mode of XP Setup.
XP Setup FAILED as described earlier ....

It means that the cmd trick as proposed by cdob will remain as working solution.

This is the Grub4dos menu title 2 that I used and where XP Setup FAILED

title 2 Continue Windows XP setup
map /XP3_1102.iso (0xff)
checkrange 0x80 read 0x8280 && map (hd0) (hd1)
checkrange 0x80 read 0x8280 && map (hd1) (hd0)
map --rd-size=2048
map --mem (rd)+4 (0x55)
map --hook
write (0x55) #GRUB4DOS\x00v=1\x00XP3_1102.iso\x00\xff\x00
chainloader (hd0)+1

This post has been edited by wimb: 28 February 2011 - 11:54 PM

[daddy_fizz]

I was attempting to run this type of setup but ran into a small snag...

If I go into presetup.cmd and add the line below "DPsFound" (as suggested).

Quote

:DPsFound
start /b "Open handle to virtual CD-ROM drive." pushd "%CDDRIVE%"

Then when it goes into TXT-mode setup, it will say that it "cannot copy presetup.cmd". If I go back to an ISO where this is unchanged, it will copy the file fine (but then loses the ISO mapping in GUI setup). If I manually copy the changed presetup.cmd then GUI setup will work fine.

Any ideas why modifying presetup.cmd would make it fail to copy in TXT setup?

If I look in TXTSETUP.SIF, I see setuporg.exe and presetup.cmd listed properly under sourcedisk files (as people on other message boards suggested checking this)

Thanks

~Fizz

This post has been edited by daddy_fizz: 02 March 2011 - 09:08 AM

[cdob]

karyonix, on 28 February 2011 - 01:01 PM, said:

Or you may try FiraDisk 0.0.1.30 with ISO file name in its parameter in small mem drive.

Thanks, virtual CD-ROM survive PNP.
Install Windows XP from ISO on UFD to SATA hard disk by karyonix http://reboot.pro/13967/

I'm using

title 1 Start Windows XP setup - firadisk.img - /XP.iso
map --mem (md)0x800+4 (99)
map /firadisk.img (fd0)
map /firadisk.img (fd1)
map /XP.iso (0xff)
checkrange 0x80 read 0x8280 && map (hd0) (hd1)
checkrange 0x80 read 0x8280 && map (hd1) (hd0)
map --hook
write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/XP.iso;floppy,vmem=find:/firadisk.img;\n\0
chainloader (0xff)

title 2 Continue Windows XP setup - firadisk.img /XP.iso
map --mem (md)0x800+4 (99)
checkrange 0x80 read 0x8280 && map (hd0) (hd1)
checkrange 0x80 read 0x8280 && map (hd1) (hd0)
map --hook
write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/XP.iso;\n\0
chainloader (hd0)+1

[daddy_fizz]

Firadisk method works ok for me...

Thanks!

~Fizz