[aviv00]

ok one things ur txtsetup is not right u changed it

39 = "Driver Cache\$WIN_NT$.~BT"

try use f12 button when the system start to load the bios boot menu

and choose directly the hdd / usb that have the setup files

if its not working try change back to hdd(0)

"No previous version of Windows NT can be found..." [press F3], like so: "

i had that problem while making this but i solve it

maybe u missed do something try to make it from the guide from start

Attached File(s)

•  Windows_XP_Professional_2009_03_21_19_28_30.png (3.17K)
  Number of downloads: 27

This post has been edited by aviv00: 21 March 2009 - 11:46 AM

[jaclaz]

aviv00

Maybe you could edit your initial post adding in it some more explicit instructions, like which exact lines need to be edited, instead of this:

Quote

a. Open TXTSETUP.SIF and rename I386 folder to $WIN_NT$.~BT
WARNING!!!!! don't rename the folders in winnt dir just those are relevant to setup

or possibly attach an already edited and known to be working TXTSETUP.SIF, I could put together a simple batch to do "automagically" just the needed edits....

jaclaz

[aviv00]

mg.eggink, on Mar 8 2009, 06:02 AM, said:

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.

i found the problem DOSNET.INF should rename there too

i will post good list soon

edited:

i didnt find the problem so i find way to bypass it check in post number #1

and post a better method to solve it check method 2

This post has been edited by aviv00: 18 April 2009 - 01:27 PM

[Spewk]

None of this is getting me anywhere..
It boots, it loads all files, and when "starting windows" I just get the good ol' BSOD everytime....

I used DBAN on the HDD after several attempts, and now that the drive is wiped clean, I'm still getting the BSOD.

I tried changing the Setup data, by adding this line :
SetupSourceDevice = \device\harddisk1\partition1
And even tried changing from 1 to 0 and back, to no avail....
I don't believe the actual HDD is even being seen, honestly - but I don't get far enough to know......

[ilko_t]

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.

[Spewk]

ilko_t, on Apr 18 2009, 08:11 AM, said:

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.

This post has been edited by Spewk: 18 April 2009 - 06:52 AM

[aviv00]

mg.eggink, on Mar 8 2009, 07:02 AM, said:

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 ?

[pSycho-Y2K]

victor888, on Mar 16 2009, 04:49 PM, said:

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

Quote

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

This post has been edited by pSycho-Y2K: 16 June 2009 - 07:45 AM

[jaclaz]

pSycho-Y2K, on Jun 16 2009, 03:43 PM, said:

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/

pSycho-Y2K, on Jun 16 2009, 03:43 PM, said:

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

[doveman]

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?

[crusoe]

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.

This post has been edited by crusoe: 20 October 2009 - 05:02 AM

[doveman]

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

[aviv00]

crusoe, on Oct 20 2009, 03:51 AM, said:

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 ?

This post has been edited by aviv00: 10 November 2009 - 09:55 AM

[crusoe]

aviv00, on Nov 10 2009, 07:52 PM, said:

crusoe, on Oct 20 2009, 03:51 AM, said:

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?

[jaclaz]

crusoe, on Nov 26 2009, 04:09 PM, said:

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/...qs-t116766.html

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

jaclaz