Prev: Not Asus-specific: SATA & AHCI
Next: Intermittent lockups, need troubleshooting advice
From: Puddin' Man on 19 May 2010 13:32

I've been dragging my W2k system from <this> hardware to <that> hardware
for near 10 years now.

About 4 years ago I discovered a registry hack:

www.mostlycreativeworkshop.com/Article11.html

that, when added to another trick or 2, made it practical to transfer
W2k sp4 and many, many applications, etc to the little P4 desktop
(multi-boot) system that I now run.

So I figgered something similar should be practical on the i5-650 /
Asus P7H55D-M EVO build that I assembled over the last couple days.

I've been working with 2 500gb Samsung sata HD's. Installed one on the P4
system, copied and doctored my primary W2k sp4 image to it, booted
it on the P4 sys, applied the last of the hacks, and moved it to
the new sys. It will not boot on the Asus board, sez something like:

"reboot and select proper boot device or insert media ... and press key"

I've toyed with boot.ini, all relevant bios settings, etc. Nothing shakin'.

Anybody had similar experience? Anybody know <something> about these Asus
boards (my 1st) that I don't know? What system component generates the
"reboot" msg?

It's still all x86, ain't it?? :-)

Thx,
P

"Law Without Equity Is No Law At All. It Is A Form Of Jungle Rule."

From: Paul on 19 May 2010 14:02
Puddin' Man wrote:
> I've been dragging my W2k system from <this> hardware to <that> hardware
> for near 10 years now.
>
> About 4 years ago I discovered a registry hack:
>
> www.mostlycreativeworkshop.com/Article11.html
>
> that, when added to another trick or 2, made it practical to transfer
> W2k sp4 and many, many applications, etc to the little P4 desktop
> (multi-boot) system that I now run.
>
> So I figgered something similar should be practical on the i5-650 /
> Asus P7H55D-M EVO build that I assembled over the last couple days.
>
> I've been working with 2 500gb Samsung sata HD's. Installed one on the P4
> system, copied and doctored my primary W2k sp4 image to it, booted
> it on the P4 sys, applied the last of the hacks, and moved it to
> the new sys. It will not boot on the Asus board, sez something like:
>
> "reboot and select proper boot device or insert media ... and press key"
>
> I've toyed with boot.ini, all relevant bios settings, etc. Nothing shakin'.
>
> Anybody had similar experience? Anybody know <something> about these Asus
> boards (my 1st) that I don't know? What system component generates the
> "reboot" msg?
>
> It's still all x86, ain't it?? :-)
>
> Thx,
> P
>
> "Law Without Equity Is No Law At All. It Is A Form Of Jungle Rule."
>

Is the disk interface set to "Compatible" mode in the BIOS ?
Give that a try.

I connected my Win2K drive to a separate disk controller card, then
moved the controller card to the new motherboard. Since the driver
for that controller card had already been installed, there was no
problem with the OS being able to boot.

As long as you've got a backup image of the Win2K SP4 partition,
you could also attempt a repair install, which won't upset
any installed programs. With backups available, all options are open to
you.

Paul
From: Puddin' Man on 19 May 2010 18:31
On Wed, 19 May 2010 14:02:14 -0400, Paul <nospam(a)needed.com> wrote:

>Is the disk interface set to "Compatible" mode in the BIOS ?
>Give that a try.

In Disk Config, SATA was set to Enhanced. I changed to "Compatible"
and got the same "reboot and select ...".

>I connected my Win2K drive to a separate disk controller card, then
>moved the controller card to the new motherboard. Since the driver
>for that controller card had already been installed, there was no
>problem with the OS being able to boot.

Are you using storage on the controller card -only- for W2k?

>As long as you've got a backup image of the Win2K SP4 partition,
>you could also attempt a repair install, which won't upset
>any installed programs. With backups available, all options are open to
>you.

1.) It is like a backup of a backup. But it boots on the old P4 sys.
2.) I don't see open options. As near as I can tell, the damned thang
refuses to read my (primary, active) boot partition.

What am I missing, here?

Thx,
P

"Law Without Equity Is No Law At All. It Is A Form Of Jungle Rule."

From: Paul on 19 May 2010 22:03
Puddin' Man wrote:
> On Wed, 19 May 2010 14:02:14 -0400, Paul <nospam(a)needed.com> wrote:
>
>> Is the disk interface set to "Compatible" mode in the BIOS ?
>> Give that a try.
>
> In Disk Config, SATA was set to Enhanced. I changed to "Compatible"
> and got the same "reboot and select ...".
>
>> I connected my Win2K drive to a separate disk controller card, then
>> moved the controller card to the new motherboard. Since the driver
>> for that controller card had already been installed, there was no
>> problem with the OS being able to boot.
>
> Are you using storage on the controller card -only- for W2k?
>
>> As long as you've got a backup image of the Win2K SP4 partition,
>> you could also attempt a repair install, which won't upset
>> any installed programs. With backups available, all options are open to
>> you.
>
> 1.) It is like a backup of a backup. But it boots on the old P4 sys.
> 2.) I don't see open options. As near as I can tell, the damned thang
> refuses to read my (primary, active) boot partition.
>
> What am I missing, here?
>
> Thx,
> P

I don't think you're missing anything, but it may still help to
review the "before" and "after".

Maybe we should look at your old system for a moment, and think
about where the disk used to be plugged in. Were you using
an Intel Southbridge port on the old machine, or some other kind
of port ? I'm asking this question, to see if it is a driver issue or
not.

What was the old motherboard make and model number, and what port
where you using on it ?

My trick with the Ultra133 TX2 (IDE) card, is purely so in the move
from one motherboard to the other motherboard, I'd be assured of
having a driver in place to boot from. Win2K was booted via the
Ultra133 TX2 card on my old system, then I moved both the disk and
the card, to the new system. That means the driver is there, to work
immediately. I can then, install drivers for other port(s) on the
new motherboard, unplug the disk and move it over. Once it is booting
from a motherboard port, I can unplug the Ultra133 TX2 and put it away.

In terms of which SATA port to use on the new machine, the Southbridge
is generally split into two controllers, with some SATA ports on one
controller, and couple other SATA ports on the second. I'd probably
try the "SATA 1" port (group of four), if I was doing it, rather than
"SATA 6" (group of two).

Paul
From: Puddin' Man on 19 May 2010 23:45
On Wed, 19 May 2010 22:03:25 -0400, Paul <nospam(a)needed.com> wrote:

>I don't think you're missing anything, but it may still help to
>review the "before" and "after".

ok ...

>Maybe we should look at your old system for a moment, and think
>about where the disk used to be plugged in. Were you using
>an Intel Southbridge port on the old machine, or some other kind
>of port ? I'm asking this question, to see if it is a driver issue or
>not.

ICH5.

>What was the old motherboard make and model number, and what port
>where you using on it ?

This is per Belarc:

Processor-
2.80 gigahertz Intel Pentium 4
8 kilobyte primary memory cache
512 kilobyte secondary memory cache
Not hyper-threaded

Board: Intel Corporation D865GVHZ AAC72419-110
Bus Clock: 200 megahertz
BIOS: Intel Corp. BF86510A.86A.0075.P24.0503071605 03/07/2005

Not really certain what you mean by "port", but the Speedfan info
will probably cover that base:

I/O properly initialized
Linked ISA BUS at $0290
Linked Intel 82801EB ICH5 SMBUS at $C400
Scanning ISA BUS at $0290...
SuperIO Chip=LPC47m172
Sensor's Base Address : $0000
Scanning Intel SMBus at $C400...
ADM1027 (ID=$27) found on SMBus at $2E
SMART Enabled for drive 0
Found WDC WD800JB-00FSA0 (80.0GB)
SMART Enabled for drive 1
Found Maxtor 53073H4 (30.7GB)

The W2k image was ~23 gb on the Maxtor, was then copied (Partition Magic 7) to
the Samsung SATA drive, registry-hacked, test-booted, then transferred to the
new sys.

>My trick with the Ultra133 TX2 (IDE) card, is purely so in the move
>from one motherboard to the other motherboard, I'd be assured of
>having a driver in place to boot from. Win2K was booted via the
>Ultra133 TX2 card on my old system, then I moved both the disk and
>the card, to the new system. That means the driver is there, to work
>immediately.

Lost po' me there. You moved the controller and disk. The driver was
on the disk. How did you install it if there was no driver to read
the disk via the "foreign" controller?

>I can then, install drivers for other port(s) on the
>new motherboard, unplug the disk and move it over. Once it is booting
>from a motherboard port, I can unplug the Ultra133 TX2 and put it away.

Still don't understand "port". Maybe I've been fiddling this thing too
long. :-)

>In terms of which SATA port to use on the new machine, the Southbridge
>is generally split into two controllers, with some SATA ports on one
>controller, and couple other SATA ports on the second. I'd probably
>try the "SATA 1" port (group of four), if I was doing it, rather than
>"SATA 6" (group of two).

The manual sez Intel H55 SATA and depicts SATA1-4 and SATA5-6, grouped
differently on the board. In recent tests I connected to SATA1.

Much Thanks,
P

"Law Without Equity Is No Law At All. It Is A Form Of Jungle Rule."

 |  Next  |  Last
Pages: 1 2 3
Prev: Not Asus-specific: SATA & AHCI
Next: Intermittent lockups, need troubleshooting advice