[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference hydra::amiga_v1

Title:AMIGA NOTES
Notice:Join us in the *NEW* conference - HYDRA::AMIGA_V2
Moderator:HYDRA::MOORE
Created:Sat Apr 26 1986
Last Modified:Wed Feb 05 1992
Last Successful Update:Fri Jun 06 1997
Number of topics:5378
Total number of notes:38326

5278.0. "Problems after installing DBK MultiStart/MegaChip" by LODGE::LEN (David M. Len) Mon Dec 16 1991 14:23

    I just finished installing the DKB MultiStart ROM switcher and the DKB
    MegaChip 2000 in my rev 4.4 Amiga 2500/030.  I'm not sure if all the
    problems are shook out yet, but there is one glaring problem I have
    encountered.  The AmigaDOS 1.3 RAD disk does not survive a warm boot.
    
    Both products seem to be functioning properly i.e. the AVAIL command
    identifies 2MB of Chip RAM, and I can toggle between the 1.3 and 2.0
    ROMS.  I haven't installed 2.0 on my HD yet, I would like test out the
    hardware mods first.
    
    I had used RAD many times before installing the DKB hardware and it has
    always worked fine.  Another thing I have observed is that system will
    sometimes hang and the screen will blank to blue.  Also, the system has
    GURU'ed and when I click on the mouse button to continue the boot I
    sometimes get hung on the same blank blue screen and must do a 3-finger
    boot.
    
    I currently have a call into DKB about these problems and am waiting for
    a return call.  But in the mean time, does anyone have any suggestions?
    Also, are there any other MultiStart II users?  And have you tried
    using RAD?                                           
T.RTitleUserPersonal
Name
DateLines
5278.1LODGE::LENDavid M. LenTue Dec 17 1991 20:459
    Well, it looks like my problem with RAD: was something I should have
    known.  I remember alot of notes about needing to use the command
    setpatch r  instead of just setpatch when going to the fatter Agnus.
    
    This has corrected my RAD: problem but it brings up a new question.
    I now get an VirusX Request box indicating that the ColdCapture Vector
    is not zero, and it could be a virus in ram.  I am using VirusX 4.01.
    
    Is this what the rest of you are seeing?
5278.2It was in the doc somewhereCX3PT1::WSC017::A_ANDERSONCSC32::A_Anderson NSU/VAX DTN 592-4170Tue Dec 17 1991 21:454
    There was something about that in the VirusX doc.  I had the same thing
    after I used SetPatch r.
    
    
5278.3LODGE::LENDavid M. LenWed Dec 18 1991 11:341
    I'll check the docs, thanks for the reply.