Jump to content











Photo

Install XP from USB AFTER Booting with PE from HDD or USB


  • This topic is locked This topic is locked
316 replies to this topic

#76 wimb

wimb

    Platinum Member

  • Developer
  • 2904 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 03 October 2008 - 05:51 PM

*** Update USB_XP_Setup - v 2.04 ***

Important Changes
  • In case the XP Source is NOT on Partition 1 then USB_XP_Setup.cmd will
    propose to Copy it to Partition 1 when this is the C-Install drive.
    Thus when the XP Source is e.g. prepared with RyanVM Integrator on Partition 2,
    then it is NOT necessary to Make an USB-stick, if Install on the Local Computer is desired.
    In fact this Option makes ANY Location of the XP Source Acceptable, instead of the Partition 1 Limitation.
  • USB_XP_Setup.cmd can now also Copy RAM BootSDI IMG File to the just Formatted Install Drive,
    so that in case when XP Setup fails, there will always be the LiveXP Escape Boot Option available.
  • For an USB-stick the option to Migrate the Drive Letter in XP Setup to U:
    can now be Selected in the Main Menu of USB_XP_Setup.cmd instead of at the End of the Program.
  • The USB_XP_Setup package can also be Downloaded combined with PStart_X so that
    the Portable Tools can be conveniently launched from a Menu, which resides in the Taskbar System Tray.
    Moreover, PStart_X can be build in the LiveXP BootSDI.img File so that it is always easy available
    in the LiveXP PE Environment.

WARNING
In the LiveXP stable Project lx51808cx of amalux I noticed that the Drive Letters of Harddisk Partitions
are NOT present in the makebt\dplist.txt as produced by makebt\MBRWiz.exe /list
The result is that when USB_XP_Setup.cmd is used in the lx51808cx LiveXP PE Environment,
then identification of Harddisk Partition from Drive Letter using makebt\dplist.txt fails,
so that USB_XP_Setup.cmd cannot Continue. The Solution is to use another LiveXP BootSDI.img File.

Another test:
Run DISKPART from cmd window
DISKPART > Select Disk 0
DISKPART > detail disk

The column Ltr does NOT display the Drive Letter for the case of lx51808cx LiveXP
I don't know yet what is causing this issue, but will Continue to do more experiments.

Direct Download - USB-XP-Setup ----- Or ----- PStart-X + USB-XP-Setup


Adding Pstart_X to your LiveXP BootSDI.img File
  • Vista as OS requires to turn User Account Control OFF
  • Download and Run PStart_X.exe and Extract to PStart_X folder
  • Copy ramdisk.sys and setupldr.bin of your WinBuilder\Workbench\Common\BootSDI folder
    to your Pstart_X\USB_XP_Setup\makebt\srsp1 folder
  • Run Pstart_X\USB_XP_Setup\USB_XP_Setup.cmd
  • Select just your XP Source folder to Copy some XP files to the makebt folder
    Then End USB_XP_Setup.cmd with Quit
  • Run makebt\Mount_IMG.cmd and Select to Mount your BootSDI.img file in a Virtual Drive
  • Copy your PStart_X folder to your Virtual Drive in which you mounted BootSDI.img file
  • Use UnMount_IMG.cmd to Close the Virtual Drive and Save the Changes in your BootSDI.img file
  • Then Run Pstart_X\USB_XP_Setup\BOOT_IMG.cmd to Install your BootSDI.img file
    as Boot Option in XP boot.ini Menu or Vista GRUB4DOS menu.lst Menu
  • Reboot and Select from the Menu to Boot with your BootSDI.img file
LiveXP + Pstart_X + USB_XP_Setup.cmd - ScreenShot

Posted Image

#77 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7100 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 04 October 2008 - 09:06 AM

WARNING
In the LiveXP stable Project lx51808cx of amalux I noticed that the Drive Letters of Harddisk Partitions
are NOT present in the makebt\dplist.txt as produced by makebt\MBRWiz.exe /list


Is the first sector of bootSDI.img a MBR or a bootsector? :confused1:

In other words, is bootSDI.img a HD image or a partition or "superfloppy" image.

jaclaz

#78 wimb

wimb

    Platinum Member

  • Developer
  • 2904 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 04 October 2008 - 09:28 AM

Is the first sector of bootSDI.img a MBR or a bootsector? :confused1:

The lx51808cx BootSDI.img file has a regular NTFS NTLDR Bootsector as First Sector,
as tested by Mounting in VDK and analysed by using TinyHexer.
The BootSDI.img file was produced as normal with WinBuilder 074 in this case.

Thanks for your help, I hope we can solve the DriveLetter issue for this particular build.

#79 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7100 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 04 October 2008 - 11:06 AM

The lx51808cx BootSDI.img file has a regular NTFS NTLDR Bootsector as First Sector,
as tested by Mounting in VDK and analysed by using TinyHexer.


I'll try to rephrase.

Try mounting the BootSDI.img with IMDISK (WITHOUT specifying an offset).

If it mounts, it means that, as confirmed by your report about first sector being a bootsector, and as expected, the BootSDI.img is a "superfloppy" image, i.e. there is NO MBR, NOR partition table.

Thus MBRWizard won't work on it.

I am not sure to have clear in my mind at what stage this is used, and what it is needed for, can you briefly describe, with more details, the procedure that fails?

jaclaz

#80 wimb

wimb

    Platinum Member

  • Developer
  • 2904 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 04 October 2008 - 11:53 AM

The lx51808cx BootSDI.img file is Installed by BOOT_IMG.cmd as boot option in boot.ini on Harddisk.
After Reboot the BootSDI.img file is loaded in RAMDISK and one boots in 30 sec into LiveXP PE Environment.

Using DISKPART from cmd window
DISKPART > Select Disk 0
DISKPART > detail disk

The column Ltr does NOT display the Drive Letter of Harddisk Partition for the case of lx51808cx LiveXP
(for other builds DISKPART would display a column Ltr with Drive Letters, so the above is an ERROR)

Now:
When Running USB_XP_Setup.cmd then this batch makes use of Roger Layton's program MBRWiz.exe
I am parsing the file makebt\dplist.txt which is produced by makebt\MBRWiz.exe /list
Normally this list displays for all Harddisks the Primary partitions with their Drive Letter.
In this way I can find out what is the harddisk and partition number of the XP Source Drive specified by its DriveLetter.
The harddisk and partition number are needed to specify in TXTSETUP.SIF file where to find the XP Source.

THe problem is that for the particular case of lx51808cx BootSDI.img file
that the Drive Letters of Harddisk Partitions are NOT present in the dplist.txt file (just displaying --)
It is NOT something specific for MBRWiz.exe since Drive Letters of Harddisk Partitions are also NOT given by DISKPART

The result is that when USB_XP_Setup.cmd is used in the lx51808cx LiveXP PE Environment,
then identification of Harddisk Partition from Drive Letter using makebt\dplist.txt fails,
so that USB_XP_Setup.cmd cannot Continue.

I hope this helps to explain the problem.

So it is NOT the BootSDI drive itself or DriveLetter X: that I need or are using (the problem is NOT there)
My concern is the Drive Letters of the Local Harddisk Partitions that are missing in makebt\MBRWiz.exe /list

#81 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7100 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 04 October 2008 - 01:03 PM

I see. :confused1:

Tricky. :cheers:

Can you try running devcon?

If yes, try using harddisk.bat here:
http://www.robvander...com/devcon.html

jaclaz

#82 wimb

wimb

    Platinum Member

  • Developer
  • 2904 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 04 October 2008 - 01:08 PM

I just made a build with lx51808cx where I Unchecked All Apps.
Then the problem is gone, but now which App is causing the DriveLetter issue .....

Will try also devcon as you said. Thanks.

#83 amalux

amalux

    Platinum Member

  • Tutorial Writer
  • 2813 posts
  •  
    United States

Posted 04 October 2008 - 06:03 PM

My guess would be the older Acronis TI script which handled drive letters differently.

#84 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7100 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 04 October 2008 - 06:21 PM

My guess would be the older Acronis TI script which handled drive letters differently.

If this is the case, together with the "drive inaccessible" created by Acronis Lower or Upper filters:
http://www.boot-land...?...=5736&st=32

I will definitely put Acronis in the "bad boys" corner (where I keep ALL Partition Magic releases after 4.0 :confused1:):
http://mirror.href.c...br/2896C417.htm

By the way I strongly suspect (but I do not have actual evidence of this creating problems) that like PM does, also some releases of Acronis product use the hidden sectors to write some "strange" data.

:cheers:

jaclaz

#85 wimb

wimb

    Platinum Member

  • Developer
  • 2904 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 04 October 2008 - 07:11 PM

My guess would be the older Acronis TI script which handled drive letters differently.

Yep, that is the bad boy ! :confused1:
Thanks, a lot for Solving the Problem :cheers:

After Removing Acronis True Image Workstation 9.1 from the build
and then booting from RAMDISK with LiveXP BootSDI.img file,
the Drive Letters are displayed correctly in makebt\MBRWiz.exe /list
so that I can use the produced file makebt\dplist.txt to determine
harddisk and partition numbers of Install Target Drive and XP Source Drive.

:cheers:

wimb

#86 amalux

amalux

    Platinum Member

  • Tutorial Writer
  • 2813 posts
  •  
    United States

Posted 04 October 2008 - 08:34 PM

Glad this solved the mystery :confused1: , can you confirm if this issue is resolved in the PE version of Acronis TI script? New version present in post lx8--cx builds and uses different file support set. Thanks wimb for finding and testing and for your great tutorials :cheers:

#87 amalux

amalux

    Platinum Member

  • Tutorial Writer
  • 2813 posts
  •  
    United States

Posted 04 October 2008 - 10:22 PM

Quick, initial test seems OK with PE Acronis...
Attached File  diskpartpeacronis.JPG   43.45KB   99 downloads
(note, vol 7 not given drive ltr for test purpose)
--
More testing confirms above results :confused1: - lx72408cx was last build to use older Acronis setup, I'm happy to report subsequent builds work fine with USB_XP_Setup (current is lx92908cx)

:cheers:

#88 wimb

wimb

    Platinum Member

  • Developer
  • 2904 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 05 October 2008 - 10:25 AM

Hi amalux,

I can confirm that lx92908cx works fine with USB_XP_Setup.cmd
and Acronis True Image PE does NOT give the previously reported Drive Letter issue.

So that is all very good now. :confused1:

I had some more work to apply the autoLocalization.Script made by PSC and Galapo
which is needed in Europe to display the decimal sign in Drive Explorer and
to get non zero values in Acronis Disk Director 10

The version of WinBuilder in lx92908cx is 075 beta 4h.
The NEW autoLocalization.Script adapted by Galapo Requires 075 beta 4n or newer, so I had to Upgrade.

http://galapo.boot-l...lization.Script

This script requires 075 beta 4n or newer, I had Succes with 075 beta 4q ,
but the BootSDI.img file made with the most recent 075 beta 5h Crashed after loading in RAMDISK.

Succes ScreenShot lx92908cx

:cheers:

wimb

#89 amalux

amalux

    Platinum Member

  • Tutorial Writer
  • 2813 posts
  •  
    United States

Posted 05 October 2008 - 03:19 PM

Hi amalux,

I can confirm that lx92908cx works fine with USB_XP_Setup.cmd
and Acronis True Image PE does NOT give the previously reported Drive Letter issue.

So that is all very good now. :cheers:

:cheers:

I had some more work to apply the autoLocalization.Script made by PSC and Galapo
which is needed in Europe to display the decimal sign in Drive Explorer and
to get non zero values in Acronis Disk Director 10

The version of WinBuilder in lx92908cx is 075 beta 4h.
The NEW autoLocalization.Script adapted by Galapo Requires 075 beta 4n or newer, so I had to Upgrade.

http://galapo.boot-l...lization.Script

This script requires 075 beta 4n or newer, I had Succes with 075 beta 4q ,
but the BootSDI.img file made with the most recent 075 beta 5h Crashed after loading in RAMDISK.

Succes ScreenShot lx92908cx

:cheers:

wimb

OK, I'll include the updated autoLocalization script in the next build; now I just have to track down and test a wb-b4q! I didn't happen to catch that one in the nightly builds but I'll look around for a download link :confused1:

#90 wimb

wimb

    Platinum Member

  • Developer
  • 2904 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 05 October 2008 - 03:32 PM

OK, I'll include the updated autoLocalization script in the next build; now I just have to track down and test a wb-b4q! I didn't happen to catch that one in the nightly builds but I'll look around for a download link :confused1:

Very Good !
I have just Uploaded both files to my download folder

http://wimb.winbuilder.net/downloads/

wimb

#91 amalux

amalux

    Platinum Member

  • Tutorial Writer
  • 2813 posts
  •  
    United States

Posted 05 October 2008 - 03:38 PM

Very Good !
I have just Uploaded both files to my download folder

http://wimb.winbuilder.net/downloads/

wimb

:cheers:

Testing now, should have new build posted later today if no problems :confused1:

:cheers:

--
Bit of a snag, I'll work on it later today and, if needed, post in appropriate place :cheers:
Attached File  error.JPG   12.36KB   78 downloads

#92 amalux

amalux

    Platinum Member

  • Tutorial Writer
  • 2813 posts
  •  
    United States

Posted 10 October 2008 - 12:35 AM

Hi amalux,

I can confirm that lx92908cx works fine with USB_XP_Setup.cmd
and Acronis True Image PE does NOT give the previously reported Drive Letter issue.

So that is all very good now. :confused1:

I had some more work to apply the autoLocalization.Script made by PSC and Galapo
which is needed in Europe to display the decimal sign in Drive Explorer and
to get non zero values in Acronis Disk Director 10

The version of WinBuilder in lx92908cx is 075 beta 4h.
The NEW autoLocalization.Script adapted by Galapo Requires 075 beta 4n or newer, so I had to Upgrade.


http://galapo.boot-l...lization.Script

This script requires 075 beta 4n or newer, I had Succes with 075 beta 4q ,
but the BootSDI.img file made with the most recent 075 beta 5h Crashed after loading in RAMDISK.


Succes ScreenShot lx92908cx

:cheers:

wimb

wimb, I am still working on this issue but at present have no solution; have you come up with anything on your end? The problem is that all new beta 5's cause errors for my builds, last good tested was beta 4h; the beta 4q you sent caused error shown in previous post; is there an index of beta 4's for download? I need to test (at least) beta 4n, 4o and 4p (if exist) to see if these might work :cheers:

#93 wimb

wimb

    Platinum Member

  • Developer
  • 2904 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 10 October 2008 - 06:08 AM

Hi amalux,

I am surprised :confused1:
What I did is combine the beta 4q with your lx92908cx and lx92908cxb
but never had the problem that you describe.
I am never getting the Personalised Settings > Internet Explorer Message in Booting with LiveXP

What is causing the difference ?
I have no Internet Explorer in LiveXP. Just Opera from lx92908cx
My XP Source is XP-SP2 Professional NLD without addons. What is yours ?
The BootSDI.img file was Installed with BOOT_IMG.cmd as boot option in boot.ini menu
on SATA Harddisk NTFS XP Format or on USB-stick with NTFS HP Format with XP as OS.

I will do some more testing, but don't have other versions of beta 4 above n.

Hopefully we find a solution to this strange problem :cheers:

#94 amalux

amalux

    Platinum Member

  • Tutorial Writer
  • 2813 posts
  •  
    United States

Posted 10 October 2008 - 06:40 AM

Yes, very strange indeed :confused1:

I also have no IE installed in LXP but I do on my host; my source is the same as yours except EN of course.

The BootSDI.img file was Installed with BOOT_IMG.cmd as boot option in boot.ini menu
on SATA Harddisk NTFS XP Format or on USB-stick with NTFS HP Format with XP as OS.

I'm only testing in Qemu now but have confirmed same error in real boot from CD or USB.

I will do some more testing, but don't have other versions of beta 4 above n.

There's a good selection here (thanks to Lancelot) but I don't think it will help because I get this error with beta 4n and later but you don't :cheers:

The only clue is this error (only one)
RegWrite - root key: [HKLM] Type: [0x1] A file was not chosen from: [WB-Software\Program Groups]

RegDelete - Failed to delete registry key in: [HKLM\WB-Software\Microsoft\Active Setup\Installed Components],{4b218e3e-bc98-4770-93d3-2731b9329278}
at the end of section
Processed section [create-Blank] in file: [%BaseDir%\Projects\LiveXP\Basic\Build\EmptyHive.Script]
in HoJoPE Hives Factory script. I'll post the complete log if needed. Thanks for your help :cheers:

#95 wimb

wimb

    Platinum Member

  • Developer
  • 2904 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 10 October 2008 - 07:05 AM

I have no Error at that Section.
WinBuilder beta 4q runs without Errors.

Strange :confused1:

#96 wimb

wimb

    Platinum Member

  • Developer
  • 2904 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 10 October 2008 - 05:55 PM

I repeated the experiment by using fresh downloads and
combining the beta 4q and autoloc from my site with your lx92908cx

LiveXP BootSDI.img was build without Error.
I can confirm that there are NO boot problems here.

Just to be sure that the downloads are OK. :confused1:

#97 amalux

amalux

    Platinum Member

  • Tutorial Writer
  • 2813 posts
  •  
    United States

Posted 10 October 2008 - 07:00 PM

Thank you very much, wimb, for testing. This is, apparently, something specific to my setup; I'll keep looking till I find it but I'm glad it doesn't affect you and that all is working well :confused1:

#98 wimb

wimb

    Platinum Member

  • Developer
  • 2904 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 11 October 2008 - 09:32 AM

*** Update USB_XP_Setup - v 3.0 ***

GUI support was added for XP Folder Select and RamBoot Image File Select by
using simple AutoIt3 routines which can be used from the batch programs
in a simalar way as the Visual Basic Script routines used previously.

The advantage is that now GUI Support is available for Folder and File Select
in all 3 environments being XP, Vista and PE, so that everything is more user friendly.
Visual Basic Script could not be used in LiveXP PE Environment
and the Vista FileSelector was until now not available in my programs.

#99 amalux

amalux

    Platinum Member

  • Tutorial Writer
  • 2813 posts
  •  
    United States

Posted 11 October 2008 - 05:11 PM

Very cool! Can't wait to try it. Thanks wimb for for further improvements to your great setups. :confused1:

#100 wimb

wimb

    Platinum Member

  • Developer
  • 2904 posts
  • Interests:Boot and Install from USB
  •  
    Netherlands

Posted 11 October 2008 - 05:56 PM

Just discovered a small error in BOOT_IMG.cmd
The path for launching Folder_Select.exe was set wrongly.
Uploaded correct version.

Please download USB_XP_Setup V 3.0 again.

Direct Download - USB-XP-Setup ----- Or ----- PStart-X + USB-XP-Setup




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users