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 [ 19 | March | 2006 ]

<< Previous Message <<


Date: Sun, 19 Mar 2006 23:36:20 PST8
From: "Steven Levine" <steve53@earthlink.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Aack, help! (was: Little questions and big question)

In <20060319155942.LSQN19976.mta9.adelphia.net@[192.168.1.20]>, on
03/19/06
at 07:59 AM, "Michael Rakijas" said:

>I guess that the warning message gave me pause because my thought was
>that it was marking some sectors as bad in the HPFS file system data and
>that it simply marked a critical piece of information as bad.

It's possible that the IFS might try to do this under the covers, but
dfsee would not do this without prompting you.

>Well, good news. The machine booted fine this morning. The only thing I
>can think of is that I fell pray to the warm boot issue of the kind Tony
>was warning us about yesterday.

Beware of old wives tales. More than likely you have an intermitted
hardware problem.

>It should have occurred to me
>considering how fresh it was in mind. Oh well, I'm just thankful that
>the machine is back. The only bad news (and it's hard bad considering
>how bad it could have gotten) is that I still have the original problem.

>I see what you mean. I was looking at the SAVETO command in ver 3.4 of
>DFSEE to see if that could be used to try and copy over the problem file
>I couldn't figure out how to use the command, however.

Saveto is what you want to use.

I tried to
>identify the fnode of a file by just giving a path name (as incstructed
>in the how-to) and it says it is not implemented for the file system.

You may have forgotten to select a volume first. This works

part d:
\config.sys
saveto e:\tmp

This will save config.sys to e:\tmp\config.sys. To get past the bad
spots, you will need to tell dfsee how to handle errors so it does not
just give up.

>Should I just download 7.15 and using it during its evaluation period?

You should download it and register it. 3.4 will work, but if you run into
userland problems, don't expect me to remember how it differs from
reasonably current versions. :-)

Steven

--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.67 #10183 Warp/eCS/DIY/14.103a_W4
www.scoug.com irc.fyrelizard.com #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 <<

Return to [ 19 | March | 2006 ]



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.