said:
>
> >a maintenance partition on at some point). In any case, a couple of
> >hours later, it was done and it had found 13 errors ranging from sector
> >00244591 to 009B5863. DFSee had the following message: SN table Bad
> >Sector Scan: holds 13 sectors DFS Message 916: SN exceeds current
> >limit.
>
> None of this should have had any effect on your disk drive. The scan
> builds an in-memory table. Nothing you have said so far in any way
> implies you ask dfsee to write anything to the drive.
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.
> >Well, it now appeared as if the machine was wiped.
> >DFSee reports "Master boot record is not valid, no partitions recognized"
> >and trying to boot the machine yields an "Operating System not found"
> >message.
>
> You have problems, but it is unlikely that dfsee caused them.
>
> >Did I wipe it with the scan from 3.40?
>
> Not unless the drive malfunctioned during the scan.
>
> >Am I lost?
>
> Don't know. Let the box sit for the night with the power off. Check all
> the connectors and such in the morning. Let's see what happens. I'll
> look at the log later in the A.M.
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. 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.
> One thing to keep in mind is that since the ISO boots FreeDOS, it must use
> different drivers than when booting eCS/OS2. This can affect how dfsee
> sees the drive and if dfsee can see the drive correctly. This is why if
> one listens to my opinions, they will notice that I always recommend
> running dfsee from a booted eCS/OS2 setup. I am a firm believer that the
> testing environment should be as close as reasonably possible to the
> production environment.
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. The command help says: "SAVETO
[dir][l] = Save filedata for current file to a new file in [dir]" but what does
one to declare the current file? 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. Should I just download 7.15 and using it
during its evaluation period?
Thanks.
-Rocky
>
> Steven
=====================================================
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 [ 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.
