Path: utzoo!attcan!uunet!aplcen!samsung!zaphod.mps.ohio-state.edu!wuarchive!mit-eddie!bloom-beacon!eru!hagbard!sunic!nuug!sigyn.idt.unit.no!solan1.solan.unit.no!stigvi
From: stigvi@solan.unit.no (Stig Vidar Hovland)
Newsgroups: comp.sys.ibm.pc.hardware
Subject: Re: Apricot Computers
Message-ID: <1990Oct5.164944.4575@idt.unit.no>
Date: 5 Oct 90 16:49:44 GMT
References: <1990Oct5.153520.1@f.adelaide.edu.au>
Sender: news@idt.unit.no (Usenet news admin)
Reply-To: stigvi@solan.unit.no (Stig Vidar Hovland)
Organization: University of Trondheim
Lines: 28

In article <1990Oct5.153520.1@f.adelaide.edu.au>, ckloeden@f.adelaide.edu.au (Craig Kloeden) writes:
|> 
|> Has anyone had any experience dealing with Apricot computers?
|> Specifically, transfering information between an Apricot and
|> "normal" IBM PCs.
|> 
|> The machine we are looking at uses 3 1/2" disks that
|> can be read by a PC but when we write to these disks on
|> the PC they cannot be read properly by the Apricot.
|> (scrambles the directory)
|> 
|> Also, just how "compatable" are Apricots?
|> 
|> Any information greatly appreciated,
|> 
|>        Craig
|> 
|> --

Old Apricot computers have a completely different diskformat than on normal
IBM clones. I have solved this problem with uudecode/uuencode and a RS232 cable.
Unfortunately my computer (Apricot portable) does not have a hardware text screen.
All text output must be done with DOS or BIOS calls. I have tried a lot of
programs on the machine, but they all fails to work. Most programs write text
directly to screen memory instead of using BIOS calls.
If you find a good texteditor that works fine on Apricots, PLEASE give me a note.

Stig Vidar Hovland - stigvi@solan.unit.no