Jump to content











Photo
* * * * * 1 votes

VHD_XP_Setup - Install XP in VHD -

vhd xp

  • Please log in to reply
143 replies to this topic

#26 ktp

ktp

    Silver Member

  • Advanced user
  • 733 posts

Posted 07 July 2013 - 01:52 PM

@Zoso

I use vmdk2vhd tool found here:

http://www.softpedia.../Vmdk2Vhd.shtml

The spdrvscn utility is useful since the DevicePath registry key must contain enumerated sub-directories and not only the topmost directory.

Edit: with this setting, when booted on new machines, drivers for new hardware are automatically installed (from DriverPacks expanded in c:\D directory).



#27 wimb

wimb

    Gold Member

  • Developer
  • 2281 posts
  •  
    Netherlands

Posted 12 July 2013 - 04:13 AM

OK, and can you boot that VHD on the SSD machine and what driver does it use in that case ?

 

It would be interesting if you can solve your hardware detect issue encountered in direct XP Setup in VHD on SSD machine.

 

After booting with XP VHD on SSD machine, then can you run

 

VHD_XP_Setup\POST_FIX\SaveHwids.exe

 

and post here the produced file HWIDs.txt , so that I can study hwids related to SSD

 

@ktp

 

It would be nice to know if your SSD hwid can be found in the MassStorage DriverPack



#28 ktp

ktp

    Silver Member

  • Advanced user
  • 733 posts

Posted 12 July 2013 - 05:00 AM

@wimb

 

In fact the SSD is seen is a plain SATA hard disk, the problem I encounter was probably due to the execution from VMware environment to real hardware (different chipset, CPU?), where there is no screen displayed. I then run the process on real USB hard disk, then copy back to the VHD the 3 directories (Windows, Program Files and Documents and Settings), then it works.



#29 wimb

wimb

    Gold Member

  • Developer
  • 2281 posts
  •  
    Netherlands

Posted 12 July 2013 - 05:07 AM

How about direct Install of XP in VHD prepared by VHD_XP_Create.exe

 

Does it work for you now by only using real hardware and no vmware ?



#30 ktp

ktp

    Silver Member

  • Advanced user
  • 733 posts

Posted 13 July 2013 - 06:58 AM

@wimb

Unfortunately, with real hardware, VHD in internal disk, ISO with DriverPacks five components integrated (CPU, Chipset, Mass storage, LAN, WLAN), I still get the black screen after "Setup is starting Windows". So I do not expect direct install to VHD in USB hard disk would work.



#31 wimb

wimb

    Gold Member

  • Developer
  • 2281 posts
  •  
    Netherlands

Posted 13 July 2013 - 08:24 AM

@ktp

 

Thanks for testing. Did you check by using SaveHwids.exe that SSD hwid is found in MassStorage DriverPack ?

 

The only thing left is trying other hardware e.g. machine with SATA harddisk instead of SSD



#32 ktp

ktp

    Silver Member

  • Advanced user
  • 733 posts

Posted 13 July 2013 - 09:27 AM

@ktp

 

Thanks for testing. Did you check by using SaveHwids.exe that SSD hwid is found in MassStorage DriverPack ?

 

The only thing left is trying other hardware e.g. machine with SATA harddisk instead of SSD

Could you tell me how to do this? SaveHwids.exe gives me a txt file with PID/VID. How can I match it with MassStorage DriverPack?



#33 wimb

wimb

    Gold Member

  • Developer
  • 2281 posts
  •  
    Netherlands

Posted 13 July 2013 - 11:15 AM

- Extract MassStorage DriverPack for XP x86

- Search with XP in folder D\M for files containing text of Compatible  ID for your SATA or IDE Controller

 

PCI\VEN_1002&DEV_4380 found in file amdhdc.inf

 

PCI\VEN_8086&DEV_1E02&CC_0106 found in file iaAHCI.inf

 

If you attach your HWIDs.txt then I can check if your hwids can be found in MassStorage DriverPack



#34 ktp

ktp

    Silver Member

  • Advanced user
  • 733 posts

Posted 13 July 2013 - 11:53 AM

I found the following from SaveHwids.exe output:

============
RAID Devices
============
PCI\VEN_8086&DEV_1C03&SUBSYS_13271043&REV_05\3&11583659&0&FA
    Name: Intel® 6 Series/C200 Series Chipset Family 6 Port SATA AHCI Controller - 1C03
    Hardware ID's:
        PCI\VEN_8086&DEV_1C03&SUBSYS_13271043&REV_05
        PCI\VEN_8086&DEV_1C03&SUBSYS_13271043
        PCI\VEN_8086&DEV_1C03&CC_010601
        PCI\VEN_8086&DEV_1C03&CC_0106
    Compatible ID's:
        PCI\VEN_8086&DEV_1C03&REV_05
        PCI\VEN_8086&DEV_1C03
        PCI\VEN_8086&CC_010601
        PCI\VEN_8086&CC_0106
        PCI\VEN_8086
        PCI\CC_010601
        PCI\CC_0106
1 matching device(s) found.

=> found in :
\M\I5\cougahci.inf
\M\I7\iaAHCI.inf
\M\I6\iaAHCI.inf

Since my chipset is Intel® 6 Series/C200 Chipset, I assume that cougahci.inf is used. How can I progress?



#35 wimb

wimb

    Gold Member

  • Developer
  • 2281 posts
  •  
    Netherlands

Posted 13 July 2013 - 12:52 PM

Use rightclick to mount your XP Setup ISO in ImDisk Virtual drive

 

Open I386\TXTSETUP.SIF

 

Search for PCI\VEN_8086&DEV_1C03

 

In [HardwareIdsDatabase] section it should be found as PCI\VEN_8086&DEV_1C03&CC_0106="iastor7"

Is that OK ?

 

Check also if mounted ISO has files OEM\DPM1209.7Z and I386\PRESETUP.CMD and I386\IASTOR7.SY_

Is that OK ?



#36 ktp

ktp

    Silver Member

  • Advanced user
  • 733 posts

Posted 13 July 2013 - 01:02 PM

I just verified: everything is OK (the two points you mentioned).

Other information: on creating XP virtual machine under VMWare, if I chose latest hardware (VMware version 9), Setup hang identically. If I chose older hardware (e.g. VMware version 6), XP setup is OK.



#37 wimb

wimb

    Gold Member

  • Developer
  • 2281 posts
  •  
    Netherlands

Posted 13 July 2013 - 01:08 PM

I just verified: everything is OK (the two points you mentioned).

Other information: on creating XP virtual machine under VMWare, if I chose latest hardware (VMware version 9), Setup hang identically. If I chose older hardware (e.g. VMware version 6), XP setup is OK.

 

OK, thanks for testing.

So we know that in principle the driver could be found and for some unknown reason it does not work yet .....

 

Did you try to change BIOS Settings for SATA Controller use IDE (or Compatible) instead of AHCI or RAID ?

 

Then remains to try Install of XP in VHD on computer with other hardware .....



#38 wimb

wimb

    Gold Member

  • Developer
  • 2281 posts
  •  
    Netherlands

Posted 23 July 2013 - 09:55 AM

-
*** Update VHD_XP_Setup_77 - Install XP in VHD ***
 
 
 

- Update  - VHD_XP_Create.exe - In Grub4dos Menu use phony RAMDISK for WinVBlock to find XP Setup ISO file

 
  This is needed to prevent BSOD 44 when XP Setup ISO file is NOT loaded into RAM
  Thanks to  genetix and steve6375  http://reboot.pro/to...tage-2-install/

 

- Added   - ImgBurn as useful program to make bootable XP Setup ISO file

- Changed - Program Version - latest version is 7.7

 
 
:cheers:


#39 wimb

wimb

    Gold Member

  • Developer
  • 2281 posts
  •  
    Netherlands

Posted 20 September 2013 - 05:40 AM

-
*** Update VHD_XP_Setup_78 - Install XP in VHD ***
 
Download VHD_XP_Setup_78 - http://reboot.pro/fi...5-vhd-xp-setup/
 
Update of USB_XP_Fix.exe - Added USB 3.0 boot support for booting XP VHD from USB
 
Install USB 3.0 Drivers for XP from folder Windows\DriverPacks\C\U as integrated by DPs_BASE.exe by using KTD option.
This will add Services and CriticalDeviceDatabase Registry Values 
and according to KTD we Set DevicePath in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion
Add about 6 MB for 16 extra Drivers to boot from USB 3.0

amdhub30, amdxhc, asmthub3, asmtxhci, EtronHUB3, EtronXHCI, FLxHCIh, FLxHCIc, 
nusb3hub, nusb3xhc, rusb3hub, rusb3xhc, tihub3, tixhci, ViaHub3, xhcdrv
 
Etron(EtronHUB3 + EtronXHCI) and Fresco(FLxHCIh + FLxHCIc) and VIA(ViaHub3 + xhcdrv)
require still improvement of the registry, but all other USB 3.0 drivers are expected to work.
 
If you have Etron, Fresco or VIA USB3.0 hardware working OK for XP, 
then I would like to receive the Exported Registry for the mentioned Services,
so that I can improve the registry in my program packages by adding the missing Parameters and WDF Service registry. 
 
:cheers:


#40 Basel Sayeh

Basel Sayeh

    Newbie

  • Members
  • 28 posts

Posted 19 January 2014 - 07:47 AM

thanks for this program but

i have error

Error 60: File for drive emulation must be in one contiguous disk area



#41 wimb

wimb

    Gold Member

  • Developer
  • 2281 posts
  •  
    Netherlands

Posted 19 January 2014 - 09:20 AM

Error 60: File for drive emulation must be in one contiguous disk area

 

Such error indicates that the Target System Drive where your VHD is Created 

does NOT have enough free unfragmented space which can occur when the drive is too fragmented or the free space is too small.

 

You can try to use WinContig.exe to defragment the created VHD file.

WinContig is available e.g. here http://reboot.pro/fi...ct-make-mini-7/

 

If not possible then improve your Target System Drive by making more free space and using Piriform Defraggler - Portable

http://www.piriform....fraggler/builds



#42 Basel Sayeh

Basel Sayeh

    Newbie

  • Members
  • 28 posts

Posted 19 January 2014 - 09:56 AM

ok thanks but now i have blue screen saying loading compoments then black scren


Edited by Basel Sayeh, 19 January 2014 - 09:57 AM.


#43 Blackcrack

Blackcrack

    Frequent Member

  • Advanced user
  • 295 posts
  •  
    Germany

Posted 19 January 2014 - 09:59 AM

edit : :)

 

btw, thank you Wimb for this nice programm :)

 

best regards

Blacky



#44 Basel Sayeh

Basel Sayeh

    Newbie

  • Members
  • 28 posts

Posted 19 January 2014 - 10:00 AM

i mean this

Screenshot-Windows-XP-Setup-Install-SCSI

 

then black screen exactly after setup is starting windows


Edited by Basel Sayeh, 19 January 2014 - 10:38 AM.


#45 Basel Sayeh

Basel Sayeh

    Newbie

  • Members
  • 28 posts

Posted 19 January 2014 - 10:02 AM

aa oo uu ?

or ah a nice thank you ?

or a more worst ?

 

btw, thank you Wimb for this nice programm :)

 

best regards

Blacky

sorry for aa

reply edited



#46 wimb

wimb

    Gold Member

  • Developer
  • 2281 posts
  •  
    Netherlands

Posted 19 January 2014 - 11:16 AM

 

then black screen exactly after setup is starting windows

 

This is normal.

You just wait few minutes until hardware is recognized and

then blue screen appears that allows you to select your VHD as target for install of XP 

and then Setup continues with blue screen to copy files ...

 

XP-1.vhd has already NTFS compressed format, so you should NOT format at Setup, just keep settings

 



#47 Basel Sayeh

Basel Sayeh

    Newbie

  • Members
  • 28 posts

Posted 19 January 2014 - 12:39 PM

This is normal.

You just wait few minutes until hardware is recognized and

then blue screen appears that allows you to select your VHD as target for install of XP 

and then Setup continues with blue screen to copy files ...

it takes forever

btw i have fix for this problem

add

map --e820cycles=0

just before "map --hook"

 

http://reboot.pro/to...45b-2011-07-14/



#48 wimb

wimb

    Gold Member

  • Developer
  • 2281 posts
  •  
    Netherlands

Posted 19 January 2014 - 12:46 PM

it takes forever

btw i have fix for this problem

add

map --e820cycles=0

just before "map --hook"

 

http://reboot.pro/to...45b-2011-07-14/

 

Thanks for the Info.

Does it work now OK for you ?

 

:cheers:



#49 Basel Sayeh

Basel Sayeh

    Newbie

  • Members
  • 28 posts

Posted 19 January 2014 - 03:01 PM

it takes forever

btw i have fix for this problem

add

map --e820cycles=0

just before "map --hook"

 

http://reboot.pro/to...45b-2011-07-14/

 

Thanks for the Info.

Does it work now OK for you ?

 

:cheers:

yes



#50 Basel Sayeh

Basel Sayeh

    Newbie

  • Members
  • 28 posts

Posted 20 January 2014 - 09:09 AM

now new error message

 

Installation Failed: J:\I386\asms. The parameter is incorrect.







Also tagged with one or more of these keywords: vhd, xp

1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users