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 [ 21 | January | 2004 ]

<< Previous Message <<


Date: Wed, 21 Jan 2004 21:54:09 PST8
From: waynec@linkline.com
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Utility diskettes hanging up

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

It occurs to me that I implemented a FAT32 partition when I started using my
recently-acquired digital camera and SmartMedia reader, probably since I
last used my utility diskettes. I can boot either WinXP or OS/2, and they
can both access the FAT32 partition where I store photos. Actually I have 2
FAT32 partitions, but one is marked as hidden. Could FAT32 be the "something
is different" reason my utility diskettes hang?

If partitions are marked hidden, will that affect the utility diskette boot
(I don't think it has, in the past); ie, could I use dfsee to mark the
currently unhidden FAT32 partition as hidden to remove it as a possible
cause and thus determine if it is the culprit?

Wayne

>>>>>>>>>>>>>>>>>>>>>>>>>>>>> prior posts:

waynec@linkline.com writes:

> Steven, I sent an email containing the config.sys files to your personal
> email sunday night, as I thought that's where you wanted it sent. Did you
> get the email?
>
> Wayne
>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>
> Steven Levine writes:
>
>
>> In <20040120045649.97484.qmail@miho.linkline.com>, on 01/19/04 at
>> 08:56 PM, waynec@linkline.com said:
>>
>>> I tried it again. A ctrl-esc shows only these tasks running:
>>
>> As I said, something is running. Is locking the driver because something
>> is referencing it. You probably have Desktop objects referencing files
>> on
>> the partition. It really does not matter what it is. You are unlikely
>> to
>> be able to change this.
>>
>>> Regardless of that, I need to get the diskettes working.
>>
>> True, since you don't have a maintenance partition.
>>
>>> haven't used the dvd under it, either. Both drives have been on the
>>> machine since I built it. I just checked, and I'm able to read cdroms
>>> from both drives under OS/2.
>>
>> Hard to say what's causing the hang since the diskettes used to work.
>> Make sure you have CDs in both drives. It might be hung trying to access
>> the driver. Make sure the driver versions on the diskette match what you
>> are using on the hard drive.
>>
>>> I have been contemplating adding an HP scsi cdrw... anyone know if I'd
>>> be
>>> able to get that working (writing) under OS/2?
>>
>> I use a Yamaha SCSI CDRW. Works fine.
>>
>>> OK, alt-F4 worked, with the same list of loads... it stops and asks me
>>> to push a key before each load, putting out the same messages as I
>>> listed previously, with the pause before each... \os2cdrom.dmd never
>>> comes back to another pause message. The os2cdrom.dmd program on the
>>> diskette has the same date and size as the one in use on my normal
>>> system: 10/18/02 and 40156 bytes.
>>
>> That confirms that CD ROM access is the problem. E-mail me a copy of the
>> config.sys for the normal boot and for the diskettes. Maybe I'll see
>> something.
>>
>> You can always disconnect the CD drives at the cable and see if that is
>> sufficient to allow you to boot.
>>
>> Regards,
>>
>> Steven
>>
>> --
>> ----------------------------------------------------------------------
>> "Steven Levine" MR2/ICE 2.41 #10183
>> Warp4/FP15/14.093c_W4
>> www.scoug.com irc.webbnet.info irc.fyrelizard.org #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
>> "rollin@scoug.com".
>>
>> =====================================================
>>
>>
>
>
> =====================================================
>
> 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".
>
> =====================================================
>
>

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

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

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


<< Previous Message <<

Return to [ 21 | January | 2004 ]



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.