SCOUG-HELP Mailing List Archives

<< Previous Message <<

Date:	Sun, 19 Aug 2001 17:29:20 PDT
From:	"mrakijas" <mrakijas@oco.net >
Reply-To:	scoug-help@scoug.com
To:	<scoug-help@scoug.com >
Subject:	SCOUG-Help: Ongoing saga

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

This is a follow up to the question I was asking at

the last SCOUG meeting.

Quick recap: I'm doing a motherboard upgrade

underneath an existing Warp 4, FP14 system. Much of

the system will be the same as before, a few

components will be changed in the process. None of

these changes should effect anything but just for

reference here are the changes: there will be a new

AGP S3 Trio3D card since the machine is going from
VLB to PCI (I was going to reload VGA via Alt-F1)

and a new DLink PCI netcard (which I can change

after the next reboot). I couldn't even get to the

white OS/2 blob when booting to the existing hard

drive.

Likely problem: Probably a drive geometry/LBA

translation/FDISK difference from the old MB to the

new.

What I've done: I attached another smaller but

still sufficient hard drive to the system as a

slave. I booted to floppy, partitioned,
formatted and "xcopy /h /o /t /s /e /r /v"ed all the

old files to the new drive. I then SYSINSTX to what

was then D: and shutdown. I disconnected the

original drive, reconfigured the new drive as a

master, reset the CMOS appropriately and rebooted.

The white OS/2 blob reappeared and the boot process

began, however, it soon stopped. "OS/2 is unable to
operate your hard disk. The system is stopped. Fix

the problem and reboot." or something to similar

effect. I tried the same thing on the original

drive (i.e. SYSINSTX to the original drive, reset

CMOS and rebooted) and got the same result.

Symptom diagnosis: I Alt-F2'ed to see the driver

loading sequence and the best I can tell, it gets

past IBM1S506.ADD and IBMIDECD.FLT but may be

halting at OS2DASD.DMD or in the similar vicinity.

Anyone see anything like this or have any ideas?

Thanks in advance.

-Rocky

____________________________________________________
__
Sent via the oco.net WebMail Server

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

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

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

Return to [ 19 | August | 2001 ]

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.