From: Andrew Wiskow (drewbrasil_at_yahoo.com.br)
Date: 2006-12-15 19:28:37
I'm not really sure if the problem was a conflict with the ROM version, or if the ROM chip in that drive was just failing. All I know is that with the 03 ROM, whenever it was hooked up with multiple drives, any drive access to any device would cause the C64 to hang. I took the drive to a friend's house who has a C128, and on his system, it seemed to work fine. I don't have a VIC-20, so I wasn't able to test it on that. I only have C64's at my house. I tested it on two C64's and one C64c, and it didn't work on any of them. But, after changing to an 05 ROM, it now works just fine. -Andrew --- Marko Mäkelä <email@example.com> escreveu: > On Fri, Dec 15, 2006 at 07:45:39AM -0300, Andrew > Wiskow wrote: > > Well, for anyone who may care, my problem has been > > solved! I tried changing out the 901229-03 ROM > chip > > in the VIC-1541 with a 901229-05 ROM chip, and now > the > > drive works perfectly! This had be scratching my > head > > for quite a while, so I'm so happy that it's > working > > now. :-D > > Very interesting. What were the exact symptoms? > Did you > try the drive with a Vic-20 in a multi-device setup? > > At > http://www.zimmers.net/anonftp/pub/cbm/firmware/drives/new/1541/ > you can read my characterization of the 901229-03 > firmware: > > 'The firmware of an old-style 1541 with long board. > This ROM has an > autobooting feature: if CLK and DATA are held low > during bootup, the > drive will wait for them to raise, and execute a > "&*" command.' > > You can also obtain 901229-01 and 901229-02 from > that location. > I never come across to a 901229-04. > > Marko > > Message was sent through the cbm-hackers > mailing list > __________________________________________________ Fale com seus amigos de graça com o novo Yahoo! Messenger http://br.messenger.yahoo.com/ Message was sent through the cbm-hackers mailing list
Archive generated by hypermail pre-2.1.8.