[Coco] Error 251

[Stephen H. Fischer]

Hi,

Do your DSAVE to a file on another disk.

OS-9:DSAVE /X0 >/D2/DSAVE.saved

Then you can look at it with an editor, I use Colorful Sled or move it to Windows with EmuDisk or CoCoDskUtil or ...

I suspect you may have a file length too big or a line length to too big.

If the text file shows no problem you can edit the "dsave.saved" into smaller files.

My normal mode of using DSAVE is:

OS-9:DSAVE /X0 ! tee dsave.saved

Ann then after perhaps some editing:

OS-9; <dsave.saved

Or just tell DSAVE to just do parts of the disk.

(The X0 is just for this post, you need to put the actual disk in there.)

SHF

----- Original Message ----- 
From: "Tim Fadden" <t.fadden at cox.net>
To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
Sent: Saturday, March 07, 2015 9:57 AM
Subject: Re: [Coco] Error 251


>I also have this problem when doing dsaves from hard drive sized drive 
> wire images (over 100 meg)  to my hard drive.  not just an sdc problem.  
> dsave gets lost, not changing directories properly and putting files in 
> the wrong place. Hard drive to drive wire seems not to have the problem. 
> Using Super driver with TC3 controller.
> 
> Just saying.
> 
> Tim
> 
> On 3/6/2015 7:08 PM, Kip Koon wrote:
>> Hi Bob,
>> I have not gotten any error 251s on my system.  Exactly what is your setup and what were you doing so I can try to reproduce your situation.  Other than the dcheck below, are there any other situations that produce error 251?
>>
>> Kip Koon
>> computerdoc at sc.rr.com
>> http://www.cocopedia.com/wiki/index.php/Kip_Koon
>>
>>
>>
>> -----Original Message-----
>> From: Coco [mailto:coco-bounces at maltedmedia.com] On Behalf Of Bob Devries
>> Sent: Friday, March 06, 2015 7:33 PM
>> To: CoCoList for Color Computer Enthusiasts
>> Subject: [Coco] Error 251
>>
>> Hi All,
>>
>> I am frequently getting ERROR 251 on my NitrOS9.
>> I'm running Nitros9 v3.3.0 on my CocoSDC.
>>
>> Has anyone else experienced this?
>> ERROR 251 is Disk ID change. I can see this happening on a floppy
>> system, but it should never happen on a hard disk system, which the
>> CocoSDC essentially is.
>>
>> Maybe a raw error is not being trapped somewhere in the drivers?
>>
>> As an example, I ran DCHECK with this command line:
>>
>> dcheck -w=/sda /dd
>>
>> That almost worked fine, however, it stopped with error 251, and did not
>> delete the temporary file /sda/dcheck030
>>
>> Regards, Bob Devries
>> Dalby, QLD, Australia
>>
> 
> 
> -- 
> Tim Fadden
> "Hey Schmidt, don't forget about the six P's.
> Proper Preparation Prevents Piss-Poor Performance!"