472 replies to this topic

[Sha0]

Which changes should I make to menu.lst to start XP-2.img on HDD-1 second primairy partition ?

(hd0) == HDD-1 == INT 0x13 drive 0x80. (hd0,0) == HDD-1, first partition. So:

title Boot XP Image - XP-2.img - WinVBlock FILEDISK

  # Use HDD-1, second partition.  This is the only change.

  root (hd0,1)

  # Sector-mapped disk

  map /XP-2.img (hd0)

  # Dummy WinVBlock parameter disk

  map --rd-size=2048

  map --mem (rd)+4 (0x55)

  # Commit mapped drives

  map --hook

  # Tell WinVBlock the filename to switch from sector-mapped to file-backed

  write (0x55) #GRUB4DOS\x00v=1\x00XP-2.img\x00\x80\x00

  # Boot the Windows in the image file

  root (hd0,0)

  chainloader /ntldr

And which changes should I make to menu.lst when I wish to start XP-2.img on HDD-2 with one primairy partition

There is limited support for this with WinVBlock. WinVBlock will take the first physical disk that meets (or exceeds) the size requirements for the sector-mapped disk, and will assume that such disk is the backing disk. If HDD-1 is bigger than the image file (of course it is), then it will be chosen as the backing disk. This is because there isn't currently any way to tell WinVBlock which physical disk to use as the backing disk.

[hemmes]

Wimb,

In your instructions item 7. you say, copy XP-1.img to bootable USB-drive.

Do you mean that I have to create an active ntfs USB-drive by myself, and then install with Grubinst_gui.exe the MBR and copy grldr to root of USB ?

Should 'USB_XP_Fix.exe' automaticly create the MBR and copy grldr to root of USB-drive ?
In tried the exe several times, but I had to create MBR and copy grldr manually.

Can you help ? Thanks a lot.

[Wonko the Sane]

Using hddimage alpha 08 my comparison of fc is as follows:

Comparing files E:\7gbwimb.mbr and E:\7GBMANUAL.MBR
000001B8: 18 E2
000001B9: 10 75
000001BA: 18 B6
000001BB: 10 65

Which should mean that now the two thingies are now the "same" .
Try starting the install of XP and stop after having formatted the image in text mode.
Extract the PBR's and compare them.
Or, under 7, format the partition under VSS and then run bootsect.exe /nt52 on the mounted image, then extract the PBR's and compare them.


Wonko

[TheRookie]

Hi Mr. Wonko,

just to have things clear...
My appoligies, I've accidently deleted the images of yesterday and have created them again, hence I have posted the mbr and pbr's of them.
I presume the mbr will be the same.

mbr results:

Comparing files E:\7gbwimb.mbr and E:\7GBMANUAL.MBR
000001B8: 22 AE
000001B9: 9C EE
000001BA: 22 CA
000001BB: 9C 06

and here are the pbr results, after mounted, formatted and applied the ntldr bootcode:

Comparing files E:\7gbwimb.pbr and E:\7GBMANUAL.PBR
00000048: 8E DC
00000049: E3 E2
0000004A: E1 76
0000004B: 28 02
0000004C: 0E F1
0000004D: E2 76
0000004E: 28 02
0000004F: E0 08

[Wonko the Sane]

VERY good.

We are now where we wanted to be :
http://reboot.pro/13731/page__st__229

The ONLY differences between your manually made image and the one pre-made by wimb are now the expected ones, the Disk Signature (which is "unique" to each HD) and the volume serial (which also is "unique" to each volume/filesystem).

NOW you can go on, and test this newly created image.
Results of tests should NOT differ from those obtained by using the pre-made image, or *something else*, NOT connected to the actual image or it's partitioning and formatting is the problem .

If the tests are successful, you can then test creating bigger images with this method.

To be really strict, for unknown reasons 2K/XP Disk Signatures have shown a tendency to have a kind of "simmetry" or "repeating pattern", see here:
http://mirror.href.c...Win2kmbr.htm#DS
but I have never seen any problem with any Disk Signature not complying with this apparent common structure.
In any case it is still possible to further modify the batch to create a "symmetrical" value.


Wonko

[Jim Cease]

I have been following this thread for a bit. Cant this be another project that can be completed in winbuilder or would this be too complicated as the way we generally do installs in XP? Can the scripts used to build apps in say PE be migrated to do an install in XP?

[TheRookie]

Hi Mr. wonko,

I'm glad to know that everything seems to be fine for you with regard to the image and that you managed to fix the critical cylinder problem.


But for me...


I install xp to the manually made image which is the exact size of Wimb's 7gb.
All seems to be fine as expected.
I can restart a number of times without any problems...

But...
appoligies for making you angry,
With regard to jaws being installed, and making a few settings in the program, after a restart,
I still get the 0x0000004e.


I don't know what to say...

Maybe you know better,
Could it perhaps have something to do with the simmetry issue?

Regards,

[Revays]

Hello Wimb,

I used IMG_XP 2.2

With IMG_XP_Create.exe I made XP-1.img and reboot.

Setup Windows XP finished well.

After I did steps

5. Install missing drivers with DriverForge and Reduce size and improve settings as usual
- Set System Restore and Windows Update Off and Run PURGE_DLLCACHE.BAT to delete 350 MB of dllcache folder
- Reduce Size e.g. Change Virtual memory and Sleep settings to get rid of pagefile.sys and hiberfil.sys
6. Connect USB-HDD where you want to use XP Image, so that USB-HDD settings are known in XP registry, and Reboot
7. Reboot with other OS and copy XP-1.img to bootable USB-drive and create entry in Grub4dos menu.lst
8. Run USB_XP_Fix.exe and Select your XP-1.img file on USB-drive and click GO
9. Reboot from USB and Select Boot XP Image - XP-1.img - WinVBlock FILEDISK

On other PC I got a BSOD (0x0000007B)

Is it normally or I forgot to do anything?

[wimb]

On other PC I got a BSOD (0x0000007B)

Can you boot XP-1.img from USB when connected to PC where you Installed XP in the XP-1.img file ?

Try this first before connecting to USB on other PC.

[TheRookie]

Hi people...

As if bad luck can't get enough of me, I am having a problem booting xp-1.img from USB.

I install xp to the 7gb image i create with Img xp
I then install xxx to the image and all is well.
I then copy the xp-1.img to the usb hdd (western digital 120 GB)
I then run USBFix and reboot in to grub installed on the uSB hdd to boot the image.
Then... I get the infamous
0x0000007b error.

I have tried using the different boot options in the menu presented i.de. multi-core compatible for most systems, single core etc.
Please could anyone help me?

Regards,

[wimb]

Then... I get the infamous
0x0000007b error.

Are you sure you did step 6 before copying XP-1.img to USB drive ?

6. Connect USB-HDD where you want to use XP Image, so that USB-HDD settings are known in XP registry, and Reboot

http://www.911cd.net...showtopic=23553

[Wonko the Sane]

Could it perhaps have something to do with the simmetry issue?

I find it strange, but everything is possible.
Try replicating the SAME signature wimb's image has.

Use MBRFIX, or a hex/disk editor to change disk signature, or re-start (again ) from scratch replacing this snippet in hddimage.cmd (alpha 0.8):

:DISKSIG

echo 01> %1

CALL :RAND Sig00

CALL :RAND Sig01

CALL :RAND Sig02

CALL :RAND Sig03

ECHO Disk Signature is: %Sig00%%Sig01%%Sig02%%Sig03%

bpatcher.exe %1 00 %Sig00% > nul

bpatcher.exe %1 01 %Sig01% > nul

bpatcher.exe %1 02 %Sig02% > nul

bpatcher.exe %1 03 %Sig03% > nul

GOTO :EOF

With the simplified:

:DISKSIG

echo 01> %1

bpatcher.exe %1 00 AA > nul

bpatcher.exe %1 01 BB > nul

bpatcher.exe %1 02 AA > nul

bpatcher.exe %1 03 BB > nul

GOTO :EOF

(changing the AA and BB to suitable values if needed)

Anyway something is still not clear to me.
The 7gbwimb.mbr once had Disk Signature 229C229C and another time 18101810 (both "symmetrical") which means that you generated two different 7gbwimb images, and that they alway use a "symmetrical value".

But I don't think that is the problem.

It is more likely that is something connected to building under windows 7 (or using VSS under it).
But right now I have NO idea WHAT could it be.


Wonko

[TheRookie]

Hi Mr. Wimb,

I can assure you that I connect the USB hdd to windows xp and also restart with it so that it is known in the windows registry.
I do this because on a second partition on the USB hdd, are all my programs that I have installed to the xp image.
Can you perhaps suggest something else that you might know of please?
Just to add, although not much relevance.
I find it strange that if I wish to run xp from USB hdd without an image i.e. where windows is installed to the drive rather than in an image. all works excellent with your magic tool.

Hi Mr. Wonko,

I will definitely try the things you have suggested about the disk signature in your post, and I think but I would not know, perhaps you are right in that vss could be part of the problem.
I'm thinking to perhaps create mount, and format the image using hddimage under windows xp to see if it would have any difference?

Also, what I find strange is that, if I create an image of 7gb using Wimb's tool, and then convert the image using Karyonix's raw2vhd and then resize it to say 10gb as an example, all works fine.
:confused:
But if I create a vhd using disk management or diskpart, and install windows xp and what-ever then I get the crash.

Hey Mr. Wimb,
If you do read this,
I'd really really like to know how you prepare the images found in IMGXP magicly please!

guys.

[Wonko the Sane]

I'm thinking to perhaps create mount, and format the image using hddimage under windows xp to see if it would have any difference?

Yes, that would be a nice confirmation that simmetry of disk signature is unrelated.

Also, what I find strange is that, if I create an image of 7gb using Wimb's tool, and then convert the image using Karyonix's raw2vhd and then resize it to say 10gb as an example, all works fine.
:confused:
But if I create a vhd using disk management or diskpart, and install windows xp and what-ever then I get the crash.

Really cannot say, the most likely thing is something connected with the NTFS permissions and/or "Recycle Bin" and/or pagefile.


Wonko

[Sha0]

With regard to jaws being installed, and making a few settings in the program, after a restart,
I still get the 0x0000004e.


I don't know what to say...
Regards,

Sometimes I repair computers for friends and family where they are complaining about such a Blue Screen of Death. It often turns out that they downloaded some software via the BitTorrent system and, of course, the software contains a nasty virus that causes the BSoD. I remove the software and the virus, advise them against downloading software via torrents, then move on. Does this apply to your scenario at all?

[TheRookie]

Hi Mr. Shao Miller,

That is some good advice you give to the people, since how offten are people tempted to have all the downloads yet are not aware of the dangers if not looked carefully that come with torrents etc.
I also relate warez which is usually found with software torrents.

That said, I don't use warez, but we all must have seen in some point in time when doing searches on google as an example to see results such as torrents containing warez.

I download jaws from:
www.freedomscientific.com
which is a legit website and I certainly trust that their software contains no viruses as such,.


OH, and one more thing Mr. Shao if you don't mind...
Is it necessary for the removable disk A to be present in my computer when using an image with WinVBlock?
I really have no problem with it being there, but was just wondering if there is a possibility to remove it?

Regards,

[Sha0]

I download jaws from:
www.freedomscientific.com
which is a legit website and I certainly trust that their software contains no viruses as such,.

Ok, the scenario I described is not likely your issue, then.

OH, and one more thing Mr. Shao if you don't mind...
Is it necessary for the removable disk A to be present in my computer when using an image with WinVBlock?
I really have no problem with it being there, but was just wondering if there is a possibility to remove it?

I believe that is most likely due to your GRUB4DOS' MENU.LST file. It's probably the drive 0x55 showing up as a disk. That should definitely be removed in a future version of WinVBlock, since it's not a real floppy disk. Thanks for the reminder. What you could do in the interim is to remove the drive letter using Disk Management. At least that way, it wouldn't be shown in My Computer.

P. S. I'd personally appreciate it if you removed my last name from your previous post. Not a big deal, but just a preference.

[davlak]

well I must confirm what TheRookie wrote.
no way to boot xp-1.img on usb.
in any case I obtain a bsod 7b. (made dozens attempts)
I am more than sure to do exactly the right things.
the only working trick for me is the usboot.org one.
the strange is that the issue happens with 7gb img in filedisk, whilst little ramdisks (i.e. 1.6Gb) seem to work.

[TheRookie]

Hi Mr. Shao,

Sorry about using your last name in my previous post.
Unfortunately I can't edit my previous post, hence I am unable to remove it.

I guess I prefer using people's names if I know them, out of respect.
No matter what the nick is I prefer to use the name.
But I guess that's just me.

@Davlak, glad to know I'm not alone having this problem.

[Sha0]

the strange is that the issue happens with 7gb img in filedisk, whilst little ramdisks (i.e. 1.6Gb) seem to work.

With a sector-mapped or file-backed disk, the backing device must be driven, and every device along the device path to the backing device must be driven, too. If your USB storage device is not being driven, then the USB storage device is not available as the backing storage to the sector-mapped or file-backed disk.

With a RAM disk, there are no extra devices to drive; the memory with the disk image is simply available.

[wimb]

@all

For 7 GB Image file you need to use other grub4dos version of grldr

IMG_XP package has grldr of 2009-10-16 (current_release version grub4dos-0.4.4-2009-10-16.zip)
What you need for 7 GB files is grub4dos-0.4.5b-2011-02-19.zip

http://nufans.net/grub4dos/tinybit/

Replace grldr and grldr.mbr in your boot drive and in IMG_XP folder with the version of folder grub4dos-0.4.5b-2011-02-19

That will work OK for 7 GB files. I just did Install XP in 7 GB file.

Please Redownload IMG_XP package and use it to update your grldr in boot drive.

The new IMG_XP package contains version grub4dos-0.4.5b-2011-02-19

Download - IMG_XP

Thanks to agni for indicating the need to update grub4dos in case of 7 GB Image files.
http://reboot.pro/98...post__p__122765

[davlak]

@all

For 7 GB Image file you need to use other grub4dos version of grldr

IMG_XP package has grldr of 2009-10-16 (current_release version grub4dos-0.4.4-2009-10-16.zip)
What you need for 7 GB files is grub4dos-0.4.5b-2011-02-19.zip

http://nufans.net/grub4dos/tinybit/

Replace grldr and grldr.mbr in your boot drive and in IMG_XP folder with the version of folder grub4dos-0.4.5b-2011-02-19

That will work OK for 7 GB files. I just did Install XP in 7 GB file.

Hi wimb...actually I was already using the patched karyonix grldr and\or the 2011-02-19 release


@Sha0

beg your pardon, effectively I wrote

the strange is that the issue happens with 7gb img in filedisk, whilst little ramdisks (i.e. 1.6Gb) seem to work.

while I was meaning filedisks in both cases. it was a copy-paste error.
I've been using 1 - 1.6 gb IMGs that I previously mem mapped and in a second moment direct mapped.
moreover I've been testing again and again, and also the 1 and 1.6gb filedisk get bsod but less frequently.
this is important IMO.
and again: the trick of usboot.org guys seems to work anyway, with any kind of USB storage device and changing PC too (even totally HW different), while IMG_XP's fix usb or even manually applying registry tweaks and usbootwatcher don't.
all the filedisks have been created through IMG_XP 2.3 (that I consider a GREAT SOFTWARE and I'm more than sure to have done all the right things.
I'm not sure, of course, but I guess there's something in winvblock and\or IMG_XP (or in the combination of both) that averts the img to be really "universal" mainly in the usb fixing.
hope is clear that I greatly appreciate winvblock (and firadisk too) and all the work needed in development and my intention is merely to send a feedback.
thanks.

EDIT: almost forgetting one important thing: VHDs work fine changing HW and sometime on USB:

title Windows XP Pro Avvio da 10GB VHD (WinVBlock - Grub4Dos)

find --set-root /xp_W.vhd 

map /xp_W.vhd (hd0) 

map --hook 

root (hd0,0) 

chainloader /ntldr



title Server 2003 Avvio da 10GB VHD (WinVBlock - Grub4Dos)

map /2003_W.vhd (hd0) 

map --mem /winvblock.ima (fd0) * 

map --hook 

root (hd0,0) 

chainloader /ntldr

* - 2k3 VHD in my tests always needs map --mem /winvblock.ima (fd0)

[Revays]

Can you boot XP-1.img from USB when connected to PC where you Installed XP in the XP-1.img file ?

Try this first before connecting to USB on other PC.

I tryed boot XP-1 img from USB flash drive (on the PC where was Installed XP) and got BSOD again.
Then I detached local HDD, boot again and BSOD didn't appear.

[sara - pmedia]

Hello everyone
i use ewf To keep my small_xp.vhd safe and small(0.9gb)
(That's how I get rid of new drivers Are added each time i boot into new machine)

also i set "My Documents" to d:\"My Documents" instead of c:\ (That's how I has enough space to work with, without "ewf filter" for downloads ect... )

i want also to set %desktop% or even the entire %user profile% to drive d:\

it is possible to set it? (maybe registry tweak...?)

I have been found Recommended for everyone

[Sha0]

i want also to set %desktop% or even the entire %user profile% to drive d:\

it is possible to set it? (maybe registry tweak...?)

I have been found Recommended for everyone

You might also enjoy the HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\ProfileList\ key, where you can redirect the entire profile, including the user's Registry (NTUSER.DAT).