SCOUG-HELP Mailing List Archives

<< Previous Message << >> Next Message >>

Date:	Thu, 30 Sep 2004 11:28:12 PDT7
From:	waynec@linkline.com
Reply-To:	scoug-help@scoug.com
To:	"Scoug Help Group OS/2" <scoug-help@scoug.com >
Subject:	SCOUG-Help: Wierd bootup hang (Warp & WinXP)

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.
=====================================================

I have had my system set up with WinXP and Warp fp15 bootable via IBM's boot
manager for about 18 months. Both operating systems and the boot manager are
resident on an ide HD; there are also 2 scsi HD's.

I was away for an extended vacation period over the summer. On my return, I
booted WinXP via boot manager, and (by way of possible explanation for
problems that followed) shortly thereafter the freebie Kerio firewall I have
been using asked me to download the latest version, 4.1.0. I did, and upon
applying the update, the installer asked if I wanted to reboot to make the
change effective. The reboot hung up (sorry, I can't remember exactly how, I
think with a blank screen), so I rebooted again and boot manager and WinXP
came up normally. But, from that point on, boots hang up on a "verifying MDI
data pool" message (or maybe it is "verifying DMI", I can't recall), which
is apparently the last thing the bios does before actually booting the hard
drive. Subsequent bootup retries are unsuccessful in the same way.

I made no other changes in hardware or software upon my return from
vacation.

The only way I've been able to get past the bootup hang is to alter the bios
boot sequence to boot dfsee from a cdrom, then use dfsee's edit capability
to force a boot of the OS/2 partition... that requires me to alter the bios
again while rebooting to take the cdrom out of the boot sequence, whereupon
OS/2 comes up directly (no intervening boot manager screen), and thereafter
I can reboot and I get the boot manager screen and boot either operating
system normally. I have even powered down briefly and still got the boot
manager screen on power-up/boot. But, if I leave the machine powered down
overnight, I'm back to the hang on the bios "verifying MDI data pool"
message.

I used WinXP's add/delete programs facility to remove the Kerio firewall,
then reinstalled the original version I was using previously (4.0.13), but I
still have the bootup problem. So I am not certain Kerio is the cause. I
also used Warp's fdisk to remove and recreate the boot manager partition and
then add Warp and WinXP to the boot manager menu; same result.

Does anyone have any insight into what might be the problem? Why does it
work OK for the rest of the day after the dfsee trick, even through
relatively short power-downs of about an hour, but won't survive an
overnight power-down?

Wayne

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

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 [ 30 | September | 2004 ]

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.