aviv00

Guide - Install WinXP From HDD or USB Drive Or CD

55 posts in this topic

What does the blue screen say? This is the interesting part, not the blue screen itself ;)

If it's the 0x0000007B error try the modified ntdetect.com as mentioned in the pinned FAQs topic. Cure for other error messages are also mentioned there.

I can't test it at the moment because I'm formatting the HDD ( Well, "C" drive, anyway - I hope that's the **** hard drive or I'll be making the USB bootable again, lol...)

Got a quick link to that FAQ, by chance ? ( sorry, I'm doing 3 things here at once...)

EDIT : OK, that didn't help ( modified NTDETECT.COM )........

I have an empty C: drive with a dos partition on it now, but booting to it no other drives show up.

Edited by Spewk
0

Share this post


Link to post
Share on other sites
Hi,

I use a USB-stick (Sandisk Cruzer)

Jaclaz is right. Making a bootable USB-stick with "HP Windows Format Utility for USB Drive Key" works

I used version 2.00 and formatted NTFS.

I had no success with FAT32.

Changing BIOS-settings did not solve the asking for "missing" SP3-files

Screenshot shows file names of "missing" files.

After setting BIOS-setting back to HD-boot something strange happened.

I can not install XP now from the same USB-stick!!.

Booting is OK, files are transfered, but at reboot HAL.DLL is missing.

someone pm and told me he had the same problem

he change the volume of the cd so that what happend

i think the volume of the hdd need to be the same of the disk

btw he burned with the original volume and its got fixed

so pretty sure its the problem

anyway to fix it ?

0

Share this post


Link to post
Share on other sites
Here already such dd example in Chinese: http://bbs.znpc.net/viewthread.php?tid=550...t=dd&page=4

The 60th topic.

I translate here

dd is a strong command, personally I think this is anoter most powerfull command after map command of grub4dos.

By using the switch of "bs, skip, seek" we can copy file to file, sector to sector and the byte to byte of file, any position can be wittern (wether the file is read only or have NTFS right, Added by victor888).

Note:

1. for a complete write, the byte of target file must be more than or equal to source file.

2. The target file should be in device, no matter what the file content is.

Example:

This is a dos batch on (fd0) name path.bat:

set string=abcdefghijklmnopqrstuvwxyz

set path=¥:

goto main

:main

...

...

....

goto end

...

:end

The first line is 37 bytes (in fact, there ENTER or SHIFTLINE charactor bytes at the end of line, for the sake of demonstrating the use of dd command, the bytes are omitted.)

The second line is 11 bytes.

Then we could write any charactor to the second line.

e.x replacy ¥ in the second line to certain letter, juse do the following:

dd if=(fd0)/path.bat of=(fd0)/path.bat bs=1 skip=11 count=1 seek=46

hence, the second line was replace to set path=a:

(bs=1 means one byte as read unite,count=1 means only write one block defined by bs switch, here is one byte. skip=11 means skip 11 bytes including space. seek=46 means skip 46 bytes when write, that is write the 47 byte ¥)

Certainly, we can do booting disk this way:

dd if=/pe.img of=(fd0) or

dd if=(cd0) of=/cd.iso

Writing boot sector to imge fiel is also convenient:

dd if=(hd0,0)+1 of=/dos.img

We can study above to chang boot.ini without dificculty.

Is there any progress on this yet? I tried your dd command approach to change the rdisk value in boot.ini, but it gives me a fatal error screaming something about "Cannot write resident/small file! Enlarge it to 2KB and try again" :(

I just know you guys are on to something as I can fully understand the problem here and also searching for alternatives and manipulating the boot process for the GUI mode to start correctly without editing the boot.ini manually.

Just a quick test where I got the error:

title Windows XP SP3 - Phase 2
root (hd1,0)
dd if=(hd1,0)/boot.ini of=(hd1,0)/boot.ini bs=1 skip=22 count=1 seek=69
chainloader (hd1,0)+1

Edited by pSycho-Y2K
0

Share this post


Link to post
Share on other sites
it gives me a fatal error screaming something about "Cannot write resident/small file! Enlarge it to 2KB and try again" :(

Have you tried enlarging it?

See this example by Mdgx on how a boot.ini can be

http://www.msfn.org/board/index.php?showto...129604&st=8

"enlarged" by adding lines of text BEFORE first section.

BTW, WHICH version are you using?

Get LATEST here:

http://nufans.net/grub4dos/

Just a quick test where I got the error:

title Windows XP SP3 - Phase 2
root (hd1,0)
dd if=(hd1,0)/boot.ini of=(hd1,0)/boot.ini bs=1 skip=22 count=1 seek=69
chainloader (hd1,0)+1

Absolutely NOT relevant to the problem you are experiencing, but you can use relative paths:

title Windows XP SP3 - Phase 2
root (hd1,0)
dd if=/boot.ini of=/boot.ini bs=1 skip=22 count=1 seek=69
chainloader +1

jaclaz

0

Share this post


Link to post
Share on other sites

Is it right that I don't need to expand the files copied to I386 (IMS.CAT, NTPRINT.CAT and SP3.CAT are already expanded but the rest are .CA_)?

Is there any need to delete the TXTSETUP.SIF in $WIN_NT$.~BT after copying it to the root?

0

Share this post


Link to post
Share on other sites

Tried both method 1 and method 2 with the same result: installation fails while loading Windows NT filesystem (ntfs.sys). Nice BSOD says that windows is shut down to prevent a damage of my computer, blah-blah-blah, run chkdisk /f.

CHKDISK says that there are no problems.

ntfs.sys on setup disk has the same date and size as the one on the working OS.

Could anyone help me?

PS.

BSOD says "*** STOP: 0x0000007B (...)", so I tried to use a modified ntdetect.com as it was advised above. Result is the same however.

Edited by crusoe
0

Share this post


Link to post
Share on other sites

You say:

e. copy whole asms folder to c:\I386

but the image "after mapping and copy the files set the files (steps 2/3)" doesn't show a I386 folder.

You might like to update this image to avoid confusion :blink:

0

Share this post


Link to post
Share on other sites
Tried both method 1 and method 2 with the same result: installation fails while loading Windows NT filesystem (ntfs.sys). Nice BSOD says that windows is shut down to prevent a damage of my computer, blah-blah-blah, run chkdisk /f.

CHKDISK says that there are no problems.

ntfs.sys on setup disk has the same date and size as the one on the working OS.

Could anyone help me?

PS.

BSOD says "*** STOP: 0x0000007B (...)", so I tried to use a modified ntdetect.com as it was advised above. Result is the same however.

sorry dont have any idea what cause that

u use raid or ahci maybe ?

Edited by aviv00
0

Share this post


Link to post
Share on other sites

BSOD says "*** STOP: 0x0000007B (...)", so I tried to use a modified ntdetect.com as it was advised above. Result is the same however.

sorry dont have any idea what cause that

u use raid or ahci maybe ?

It's certainly not raid, but AFAIK ahci has something to do with usb - and SATA disks. Should I do something special if the installation target is SATA?

0

Share this post


Link to post
Share on other sites
It's certainly not raid, but AFAIK ahci has something to do with usb - and SATA disks. Should I do something special if the installation target is SATA?

0x0000007b means "unaccessible boot device".

In the case of a SATA device, please read as:

0x0000007b I miss the appropriate SATA drivers for this device

Read FAQ #3 here:

http://www.msfn.org/board/faqs-t116766.html

Add the BTS driverpack (or add the specific SATA driver) to the source.

jaclaz

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.