said:
Hi,
>No. I was away while it was working, and came back to a black screen:
>003A3002E959D69D - SYS02027-0008:0180 (that's all)
That's an odd one. I'd have to suspect that there's still a disk access
issue. That's usually what causes a sys2027
>When I re-boot from that partition, I get the same screen immediately,
>about 1-2 seconds after BM.
I guess the error is coming out of the microFSD.
>I tried a JFS boot partition. I'm going to try again with HPFS.
Is this box suitably transportable? We could fight with it on Saturday.
Steven
--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 3.00 beta 04 #10183 eCS/Warp/DIY/14.103a_W4 etc.
www.scoug.com irc.ca.webbnet.info #scoug (Wed 7pm PST)
----------------------------------------------------------------------
=====================================================
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
"postmaster@scoug.com".
=====================================================
<< Previous Message <<
>> Next Message >>
Return to [ 17 |
April |
2007 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
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.
