Install XP from USB: conquering ASUS M4A78 Pro

[Tulert]

@Tulert

Since your motherboard refuses (for now) to present USB stick as HD, are you willing to experiment another way of installing XP when stick is seen as FD?

Now back in town.

We can experiment, have to catch up with work now, Win XP in not the 1-st priority.

Edited June 29, 2009 by Tulert

[Tulert]

If it does not boot on the laptop

• use HDhacker (on the laptop) and save:
  
• MBR of the stick
  
• bootsector of the stick (first sector of logicaldrive for FAT 16/32 or first 16 sectors for NTFS)
  
• Compress in a .zip
  

Fuwi's tool with FAT16.

Results on ASUS from this setup

Access the stick from an already booted system, say it gets assigned letter G:\.

execute in Command Prompt:

DIR /S G:>C:\dirofstick.txt

Attach resulting file C:\dirofstick.txt

Boot from the stick on the ASUS,

grub4dos command prompt and type in it:

find /menu.lst [ENTER]

Results:

"Warning! FAT cluster size(=65536) larger than 32K!"

(fd0)

ls ( [TAB]

Results:

"Possible disks are: fd0 fd1 hd0 hd1 rd"

each of the "fd" and "hd" devices, always using [TAB] autocompletion features, like in:

ls (fd0,[TAB]

"Possible partitions are:

Filesystem type unknown, partition type 0x6B

Filesystem type unknown, partition type 0x20

Filesystem type unknown, partition type 0xB4

Filesystem type unknown, using whole disk"

ls (fd0,0)  [TAB]

"Error 11: Unrecognized device string, or you omitted the required DEVICE part which should lead the filename"

ls (fd0,0)/

"Error 11: Unrecognized device string, or you omitted the required DEVICE part which should lead the filename"

HDHacker_Res.zip

dirofstick.txt

Edited June 30, 2009 by Tulert

[jaclaz]

OK.

The MBR is a "standard" 2K/XP one, with the "HP hack" and with unbalanced CHS/LBA data.

First thing let's correct the unbalanced data.

Get beeblebrox:

On the laptop:

Access the stick with it.

You should see these values:

#0-0E-80-0-1-1- 490-254-63-63-7897025

change them as follows:

#0-0E-80-0-1-1-490-254 -63-63-7887852

Use Hdhacker (or the same beeblebrox) to make a backup of the modified sector.

Eject and reinsert the stick.

Format it as FAT16 with "normal" 2K FORMAT command.

Eject and reinsert stick.

Copy to it (from the C:\ partition of your laptop):

NTLDR

NTDETECT.COM

BOOT.INI

grldr (from latest grub4dos)

menu.lst (as well from latest grub4dos, the "standard" one will do for the moment)

Edit the BOOT.INI on the stick as follows:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows (dummy entry)"
C:\grldr="Grub4Dos"

Try booting on the laptop.

You should be able to see the two choices in BOOT.INI and, when you choose the second one (grub4dos) you should be able to see the choices in "standard" menu.lst.

If it doesn't boot on the laptop, re-open the stick with beeblebrox and change:

#0-0E-80-0-1-1-490-254 -63-63-7887852

to:

#0-06-80-0-1-1-490-254 -63-63-7887852

Use Hdhacker (or the same beeblebrox) to make a backup of the modified sector.

Try again booting the laptop from it.

If it works, try booting the ASUS desktop from it.

If you get to the second screenshot of post #15

http://www.msfn.org/board/index.php?showto...35364&st=14

try issuing the grub4dos commands detailed in post #18:

http://www.msfn.org/board/index.php?showto...35364&st=17

Please report.

jaclaz

[Tulert]

Try booting on the laptop.

"Disk error

Press any key to restart"

If it doesn't boot on the laptop, re-open the stick with beeblebrox and change:

#0-0E-80-0-1-1-490-254 -63-63-7887852

to:

#0-06-80-0-1-1-490-254 -63-63-7887852

For some reason I see

#0-06-80-0-1-1-490-254 -63-63-7887852

in Beeblebrox right away. I am pretty sure I changed to

#0-0E-80-0-1-1-490-254 -63-63-7887852

And when I 'restore' the saved partition table I see

#0-0E-80-0-1-1-490-254 -63-63-7887852

Repeated the procedure. After frormatting on a laptop get

#0-06-80-0-1-1-490-254 -63-63-7887852

Instead of

#0-0E-80-0-1-1-490-254 -63-63-7887852

Or am I not getting the instructions:

Format it as FAT16 with "normal" 2K FORMAT command

Edited June 30, 2009 by Tulert

[jaclaz]

No, it's allright.

In some cases, actually I cannot really remember when and why, FORMAT changes the already present:

0E -> FAT16 LBA mapped partition to:

06 -> FAT16 CHS mapped partition

or viceversa.

Empirically, 06 has been found to be "more bootable", but when you have correctly balanced CHS and LBA data, it shouldn't make much difference.

I.e. you can read my previous:

If it doesn't boot on the laptop, re-open the stick with beeblebrox and change:

#0-0E-80-0-1-1-490-254 -63-63-7887852

to:

#0-06-80-0-1-1-490-254-63-63-7887852

If it doesn't boot on the laptop, re-open the stick with beeblebrox and change:

#0-06-80-0-1-1-490-254 -63-63-7887852

to:

#0-0E-80-0-1-1-490-254-63-63-7887852

the accent is on "if it doesn't boot on the laptop", it is possible that any given BIOS:

- boots from both "06" AND "0E"

- boots with "06" BUT NOT with "0E"

- boots with "0E" BUT NOT with "06"

compare with this:

http://www.911cd.net/forums//index.php?showtopic=21049

On a "good" "wide minded" motherboard BIOS, once CHS and LBA data is "balanced" you can change 06 to 0E at will, but this does not happen always.

jaclaz

[Tulert]

If it doesn't boot on the laptop, re-open the stick with beeblebrox and change:

#0-06-80-0-1-1-490-254 -63-63-7887852

to:

#0-0E-80-0-1-1-490-254-63-63-7887852

"Disk error

Press any key to restart" for both.

Didn't reformat, only changed the partition table.

Edited June 30, 2009 by Tulert

[jaclaz]

Hmm.

I wonder what it could be the problem.

In the MBR there are these as messages in case of Error:

• Invalid partition table
  
• Error loading operating system
  
• Missing operating system
  

In the "normal" FAT bootsector there are these:

• Invalid system disk
  
• Disk I/O error
  
• Replace the disk, and then press any key
  

or these:

• NTLDR is missing
  
• Disk error
  
• Press any key to restart
  

So it seems like you are erroring out with the latest, which should mean that the bootsector data does not "match" the MBR one.

This does not make much sense, unless somehow the stick is seen with a weird geometry, but even then, it shouldn't behave like this.

I tried creating an image with your stick data and as expected it boots allright in Qemu, both with 0E and 06 as Partition ID.

A further check on your MBR shows some "garbage" between 0x180 and 0x199, and again from 0x01AB and 0x1B8, but I don't think that can be the reason.

Could it be because of the non-standard cluster size? I doubt it as well.

Can you try using a MBR I prepared on your stick?

You can use HDhacker to save it on your stick.

Procedure:

extract from tulert.zip

first1.dat, first64.dat and first315.dat

use hdhacker to write it to the MBR of the stick

eject and re-insert stick

format the stick as FAT16

check with beeblebrox the values

copy to the partition the files listed on post #33

try booting from it

if it doesn't work, try again with 0E instead of 06

If still it doesn't work, try copying the whole first64.dat file to the stick.

You will need to use dsfi (part of the dsfok toolkit):

http://members.ozemail.com.au/~nulifetv/freezip/freeware/

unzip in C:\dsfok

copy to C:\dsfok\ first64.dat

use as

dsfi \\.\PhysicaldriveN 0 0 C:\dsfok\ first64.dat

the right N is the same as the one seen in hdhacker or beeblebrox

eject and re-insert stick

try booting from it

if it doesn't work, try again with 0E instead of 06

(at least the error message should change)

If still it doesn't work, try copying the whole first315.dat file to the stick.

dsfi \\.\PhysicaldriveN 0 0 C:\dsfok\ first315.dat

eject and re-insert stick

copy to the partition the files listed on post #33

try booting from it

if it doesn't work, try again with 0E instead of 06

Right now the attachment system is not working for me, please get it from here:

http://rapidshare.com/files/250483422/Tulert.zip.html

jaclaz

P.S.: Though possibly a bit premature, can you try running ChipGenius on that "MicroCenter 4GB" and post Vid/pid and manufacturer:

http://www.boot-land.net/forums/?showtopic=4661

Latest should be v3.01:

http://dl.mydigit.net/2009/0406/chipgenius.html

http://dl.mydigit.net/down.php?a_k=LnppWmp...BQAdQN2dg%3D%3D

Edited June 30, 2009 by jaclaz

[Tulert]

...try using a MBR I prepared on your stick...

...try booting from it...

...try again with 0E instead of 06

Results:

first1.dat

.Format with WinXP format, FAT16

.After-format Beeblebrox: 06-80-0-1-1-490-254-63-63-7887852

.Laptop boot:

"Disk error

Press any key to restart"

.06 -> 0E

.Laptop boot:

"Disk error

Press any key to restart"

first64.dat

.Laptop boot:

" Rimuovere supporti

Premere un tasto per riavviare"

.06 -> 0E

.Shows Menu on grey screen, pic. ('Main Menu')

.Selected Grub4Dos, pic. ('After Main Menu')

try running ChipGenius on that "MicroCenter 4GB"

Pic. included

Commands on Asus in this post to be done

Edited July 1, 2009 by Tulert

[Tulert]

Same Stick on Asus:

BIOS: HDD or Auto => Motherboard logo

BIOS: FDD =>

. Boots up to menu

. 2-nd screenshot with Grub4Dos option chosen

Edited July 2, 2009 by Tulert

[Tulert]

Results (after an extra format, see below

but doesn't work without format either):

first315.dat

. Laptop boot

=> "Disk error

Press any key to restart"

. 06 -> 0E

. Laptop boot

=> "Disk error

Press any key to restart"

===============================================

I am afraid I messed up with the sequence in the instructions, in particular I am not sure if I formatted and copied files from #33 when I repeated the procedure for first64.dat.

===============================================

So I did 2 more "tests" with the sequence

. format

. MBR

. out/in for stick

. format

. Beeblebrox

. copy #33

. boot laptop

. 06 -> 0E

. boot laptop

first64.dat & 06

first64.dat & 0E

first315.dat & 06

first315.dat & 0E

ALL result in

"Disk error

Press any key to restart"

===============================================

Ok, I repeated everything from the beginning, i.e. from first1.dat to the end of post #38 and I am not getting those pictures any more. "Disk error. Press any key to restart" in all 4 cases. Sorry.

I did the "procedure" from the beginning for first64.dat which was wrong.

===============================================

I replicated #38. It goes

. format

. first1.dat

. format

. copy #33

. boot laptop => Disk error ...

. 06 -> 0E

. boot laptop => Disk error ...

. first64.dat

. boot laptop => Italian

. 06 -> 0E

. boot laptop => pictures

When I tried to use first315.dat from here I got error when trying to copy files in #33. WinXP refused to copy them. This is where I got freaked out and went to the start of this post, did format & full procedure described for first1.dat combined with first315.dat.

Edited July 2, 2009 by Tulert

[jaclaz]

It seems like something (unknown) prevents from "properly" creating the filesystem. But really cannot say what.

The laptop appears to "like" 0E (LBA) and not 06 (CHS), but using the first64.dat it does boot properly.

The first315.dat is identical (apart volume serial) to first64.dat but has added EMPTY FAT tables, so it should behave exactly like first64.dat.

It is possible that your laptop is one of the very few ones (I seem to remember IBM ones) that use nx240x63 geometry.

However, get back to the condition that was working (as per posted pictures).

Now you need to use a hex editor to change the embedded menu.lst in grub4dos:

http://www.boot-land.net/forums/index.php?...c=6775&st=5

http://www.boot-land.net/forums/index.php?...=7231&st=25

or grubinst as in here:

http://www.msfn.org/board/index.php?showto...134808&st=6

to change the "embedded" menu.lst in grub4dos to make it search for grldr on "floppy" too. (i.e. remove the "--ignore-floppies" from entries) in order to replicate on the Asus the same behaviour of the laptop.

For the moment, boot to the ASUS, get to command line and issue these commands:

map (fd0) (hd31,0)

[ENTER]

map --hook

[ENTER]

root (hd31,0)

[ENTER]

chainloader /ntldr

[ENTER]

boot

[ENTER]

You should get back to the BOOT.INI choices.

The other thing to try is to see if, since you have a USBest UT165 controller, the correspondent "manufacturer tool" can "flip the removable bit".

The tool should be this one:

http://flashboot.ru/Files-file-219.html

http://flashboot.ru/uploads/files/public/U...5_1.65.17.0.rar

The manual for it should be this one:

http://flashboot.ru/uploads/files/public/U...ual_EN_V4.0.rar

If it works, the stick becomes a "fixed" device, just like any hard disk, and thus the ASUS should recognize it properly.

jaclaz

[Tulert]

The first315.dat is identical (apart volume serial) to first64.dat but has added EMPTY FAT tables, so it should behave exactly like first64.dat.

Well, I did an extra 'format' in the middle because wasn't able to copy files in #33. Should have tried without copying because the old files were visible... When I did an extra 'format' for first64.dat it stopped working too, plus I didn't try to copy files in #33 in that case.

It is possible that your laptop is one of the very few ones (I seem to remember IBM ones) that use nx240x63 geometry.

I attch 2 pics for T40 with XP and a new one X61 with Vista. Don't they both look like nx240x63 ?

I need to disappear for a couple of days. If I have updates, I'll post.

[jaclaz]

I attch 2 pics for T40 with XP and a new one X61 with Vista. Don't they both look like nx240x63 ?

Yep, they do.

But the ASUS should have "correct" nx255x63

However this explains perfectly why we had the problem with CHS.

I need to disappear for a couple of days. If I have updates, I'll post.

If you want, just to make double sure, I can make a MBR with nx240x63 geometry.

"See" you when you are back.

jaclaz

[Tulert]

But the ASUS should have "correct" nx255x63

If you want, just to make double sure, I can make a MBR with nx240x63 geometry.

It's Ok for now. I have enough to test and it cuts into the other things I have to do. If you think it is something interesting to try -- I'll do it but with a delay.

Also, what does it mean "ASUS should have nx255x63"? That is it is programmed as HDD in BIOS or something like that?

Edited July 3, 2009 by Tulert

[Tulert]

... get back to the condition that was working (as per posted pictures).

... need to use a hex editor to change the embedded menu.lst in grub4dos or grubinst

... (i.e. remove the "--ignore-floppies" from entries) in order to replicate on the Asus the same behaviour of the laptop.

Did this:

Edited menu.lst in Notepad & removed all "--ignore-floppies".

Attempt on ASUS resulted in same pics as http://www.msfn.org/board/index.php?showto...st&p=867072