Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!uwm.edu!psuvax1!psuvm!dxb132 From: DXB132@psuvm.psu.edu Newsgroups: comp.sys.amiga.programmer Subject: Re: Mike Farren Tutorial. Message-ID: <91088.011544DXB132@psuvm.psu.edu> Date: 29 Mar 91 06:15:43 GMT References: <20115@cbmvax.commodore.com> <1991Mar27.012717.11541@starnet.uucp> <1998@aldebaran.cs.nps.navy.mil> <1991Mar27.175514.25590@cunixf.cc.columbia.edu> Organization: Penn State University Lines: 24 In article , mykes@amiga0.SF-Bay.ORG (Mike Schwartz) says: >I have been lobbying Commodore to solve the problem. The problem is not with >the developers, but with the OS. What I suggest CBM does is to provide entry >points in Exec for software that takes over the machine to access both the >floppy drives and the hard disks. It is easy enough for them to do for 2.0 >before it goes to ROM. It should be noted that hard drive controller firmware is almost always resident in RAM, so you can't run out of ROMs directly. (This does not make it impossible, of course). The other thing is, normal drivers depend HEAVILY on the operating system. But you're right, C= could put the right hooks in there. (Not in time for 2.0 however). An alternative, maybe better, solution is to use the AmaxII driver set. Remember, AmaxII takes over the system just like nasty games. The AmaxII drivers provide the basic functionality you need without using the operating system. (It is possible that they may use the Mac OS, but in reality they don't). The drivers are self contained and position independent. (PC relative). Well, maybe they need a little glue code, I haven't really figured them out. -- Dan Babcock