RE: Multi disk emulator

From: Baltissen, GJPAA (Ruud) (ruud.baltissen_at_abp.nl)
Date: 2003-12-10 07:54:19

Hallo Nick,


> Micheal (?) replied that DATA was used because it was more important
> for clocking in a multi-tasking system

I have no interest at all to modify my software so it will run under
Windows. So I won't have this problem :) The reason behind it: I have enough
486-66's and better laying around doing nothing. This also include some
smaller harddisks < 200 MB. And Windows occupies at least 200 MB.


> The only danger which you have to watch for is if your "emulator"
> generates ATN.

It cannot and that is a hardware matter. But anyway, a 1541 cannot generate
ATN, so an emulator shoulld not either.


> I do this to renumber device 8 for example during device swaps.

Please, explain this a bit more.

To be honnest, I haven't thought at all about the possibility to change the
devicenumber by software. Must put that on the to-do list.


--
    ___
   / __|__
  / /  |_/     Groetjes, Ruud
  \ \__|_\
   \___|        <http://Ruud.C64.org> http://Ruud.C64.org








=====DISCLAIMER=================================================================

De informatie in dit e-mailbericht is vertrouwelijk en uitsluitend bestemd voor de geadresseerde. Wanneer u dit bericht per abuis ontvangt, verzoeken wij u contact op te nemen met de afzender per kerende e-mail. Verder verzoeken wij u in dat geval dit e-mailbericht te vernietigen en de inhoud ervan aan niemand openbaar te maken. Wij aanvaarden geen aansprakelijkheid voor onjuiste, onvolledige dan wel ontijdige overbrenging van de inhoud van een verzonden e-mailbericht, noch voor daarbij overgebrachte virussen.

The information contained in this e-mail is confidential and may be privileged. It may be read, copied and used only by the intended recipient. If you have received it in error, please contact the sender immediately by return e-mail; please delete in this case the e-mail and do not disclose its contents to any person. We don't accept liability for any errors, omissions, delays of receipt or viruses in the contents of this message which arise as a result of e-mail transmission.


       Message was sent through the cbm-hackers mailing list

Archive generated by hypermail pre-2.1.8.