Xref: utzoo comp.sys.atari.st:29637 comp.os.cpm:3932 Path: utzoo!attcan!uunet!samsung!zaphod.mps.ohio-state.edu!rpi!uupsi!sunic!dkuug!freja.diku.dk!skinfaxe.diku.dk!jensting From: jensting@skinfaxe.diku.dk (Jens Tingleff) Newsgroups: comp.sys.atari.st,comp.os.cpm Subject: Re: Atari ST CP/M emulator (was 'Re: Appletalk on the TT') Message-ID: <1990Jul17.070025.19732@diku.dk> Date: 17 Jul 90 07:00:25 GMT References: <4951@brahma.cs.hw.ac.uk> <4b7dbd6f.20b6d@apollo.HP.COM> Sender: news@diku.dk (The Netnews System) Organization: Department Of Computer Science, University Of Copenhagen Lines: 22 ralph@laas.fr (Ralph P. Sobek) writes: >Wouldn't it be easier to emulate CP/M 68000? Such beasts surely exist >since I threw out our documentation. Yes, but who would want to do that ? I bought an ST to get software, even though I had a technically superior (and 20 times more expensive, originally) CP/M-68k machine.. . The only reasonable thing I can think of, for the CP/M-68k machine, is to emulate TOS (only the `normal' bits, not BIOS..) in order to run compilers etc. Anyway, CP/M-68k STINKS. It does allow for disk change without reboot, but that's about the only improvement in usability over CP/M 2.0. I can't even write a terminal emulator, since the standard BIOS doesn't have status info. for the serial line(s), arrrghh. Jens Jens Tingleff MSc EE, Institute of Computer Science, Copenhagen University Snail mail: DIKU Universitetsparken 1 DK2100 KBH O "It never runs around here; it just comes crashing down" apologies to Dire Straits