Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!csd4.milw.wisc.edu!marque!lakesys!dougm
From: dougm@lakesys.UUCP (Doug McIntyre)
Newsgroups: comp.sys.apple
Subject: Re: sys disk 5.0
Message-ID: <935@lakesys.UUCP>
Date: 6 Aug 89 02:02:34 GMT
References: <8908051759.AA11258@obsolete.UUCP>
Reply-To: dougm@lakesys.UUCP (Doug McIntyre)
Organization: Lake Systems - Milwaukee, Wisconsin
Lines: 27


	I'm also having problems with GS/OS v3.0. This is working with large
files though. Going to about 1M or so in size. Using a C program that is just 
appending files together, I have about 6 files in 350,000 character chunks.
I need to append these together to get one big file....  Under GS/OS v3.0,
on the second and later chunks, I usually get the GS/OS error box poping up
with the error: bad storage type ($4b). Also pops up an address which I 
forgot to write down.. I then can't delete this large file without an error,
(under Orca, invalid param block address..) and I lose the space taken up
by this large file, (fixed by mr.fixit).. So what is causing this?? It works
just fine under GS/OS v2.0..

Also a question since the docs aren't available from APDA yet..
What is error $64? I assume it is something with the character console
driver, since that is about where I got it..

3rd problem. I'm losing data while going out through the printer port. First
I use gsos.exerciser just for a basic tool.. I read a file of graphics data
that I generated for the printer, open the printer (after searching for it
with DINFO), and then write it out to the printer.. At about byte 2098 I start
losing 32 bytes. Then I get back into the stream, and then it procedes to lose
more chunks out of the data stream. I've also tried writing the data in 1k 
chunks. Since the buffer of an IW II is 2k there shouldn't be any buffer
overflow problems.. 
-- 
UUCP: uunet!marque!lakesys!dougm			Compuserve: 70611,2215
INET: dougm@lakesys.lakesys.COM	   GEnie: D.MCINTYRE1		 ALPE: DougMac