SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, 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.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 17 | June | 2002 ]

>> Next Message >>


Date: Mon, 17 Jun 2002 08:25:24 PST7
From: "mrakijas" <mrakijas@oco.net >
Reply-To: scoug-help@scoug.com
To: <scoug-help@scoug.com >
Subject: SCOUG-Help: Trap inquiry (final note)

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

Well, I went the whole nine yards. I booted to an old DOS disk and executed an FDISK /MBR (to disk 1 - OS/2's FDISK didn't seem to acknowledge the /MBR switch) to clear the master boot record and then deleted all existing partitions. I booted to OS/2 floppies, recreated the partitions I needed and formatted HPFS. I reconnected drive 2, rebooted and copied all files back over from drive 2 to 1. No change! Drive 1 still traps on shutdown. I guess I have to chalk this one up to the (OS/2?) computer gods not liking the one drive. More likely, I guess that some timing or tolerance changed just enough to screw things up.

Anyway, I'm still interested in ideas but I'm inclined to giving in to the swapped drive.

-Rocky

---------- Original Message ----------------------------------
From: Michael Rakijas
Reply-To: scoug-help@scoug.com
Date: Sat, 15 Jun 2002 20:13:19 PST7

>After trying all the non-invasive debug procedures I could think of, I broke
>down and opened the machine up. After reseating stuff and other fiddling with
>no behavior change, I attached a second hard drive as a slave to the original.
>Call the original drive disk 1 and the added, temporary drive disk two. After
>partitioning and formatting disk 2, I did the xcopy /h/o/t/s/e/r/v routine from
>1 to 2 after booting to floppy. To make sure that everything went as expected,
>I disconnected drive 1, reset drive 2 as master and rebooted (adjusting the BIOS
>in the process). Booting went perfectly and, even better, *NO TRAP AT
>SHUTDOWN*. Brilliant, I thought. Simply reformat disk1 and reverse the xcopy
>process and I should be good to go. So, after reconnecting disk 1 as master and
>disk 2 as slave and booting to floppy, I execute a FORMAT C: /FS:HPFS /L to make
>sure disk integrity is completely checked. I xcopy back to 1 from 2, disconnect
>2 to preserve one known good copy of the system and reboot. Although booting is
>fine, it again TRAPS AT SHUTDOWN! This is pretty screwy but fairly
>illuminating. It does seem to suggest that the rest of the hardware is okay.
>Maybe the drive is becoming flaky? I don't know - it seems to behave well
>otherwise.
>
>At this point, one has to consider just replacing drive 1 with drive 2 and
>leaving it at that. Although I will consider that, I'd like to leave it as a
>last resort since it was supposed to be a temporary solution and I had other
>plans for that drive. Is there nothing else I can try? Should I delete the
>partition on drive 1, repartition and try again or is this a waste of time? I
>know FDISK /MBR in DOS' FDISK resets the master boot record - will it do it with
>OS/2's? Would this have any value? Finally, would you say that the drive is
>faulty, maybe got a virus or is it just the combination of the drive/motherboard
>or some other drive interaction that is causing the problem?
>
>This should pretty much close it for me, though. I'll try a few more ideas
>that may come from this thread but I've got other things to do so I'll go for
>the fail safe if nothing else works. Thanks for all your suggestions and the
>help I've received with this problem.
>
>> Steven
>
>-Rocky

________________________________________________________________
Sent via Orange County Online's WebMail System at oco.net

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

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

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


>> Next Message >>

Return to [ 17 | June | 2002 ]



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.