CompuServe Thread

Multistart & AdIDE

7 messages in this thread
#74048From: Brian BartlettOct 21, 1992 3:51 AM
Dean, I ran into a slight problem with my MultiStart II for my Amiga 500. I have a Rev. 6A motherboard which also has an AdIDE/40 installed on it. Apparently, there is no way to have both the AdIDE and the MultiStart II installed at the same time, unless I'm missing something here, without using some type of socket extension. I'm willing to forgo the RF shielding, if necessary. Do you know of any place off-hand where I can get the socket extension for the ROM socket besides an electronics sales firm. We don't have one of those around here, to my knowledge. Thanks in advance. Brian ->on AutoPilot
#74153From: Dean BrownOct 22, 1992 12:10 AM
Brian, Call tech support at (313) 960-8750 and describe your problem. There is a fix for your problem and Jerry in tech support can take care of it for you. Dean DKB Software
#74412From: Brian BartlettOct 24, 1992 12:20 PM
Dean, will do. Thanks! Good products. Brian ->on AutoPilot
#74255From: Ronald B. RomineOct 22, 1992 9:14 PM
I had the exact same problem with a rev. 5 motherboard, the AdIDE/40, and MultiStart-II. The MultiStart overlaps, the CPU socket. I believe DKB makes an alternate version of the board, which uses a cable that allow the board to be moved aside. Or it might have been just a cable. Try calling them, I'm sure they are aware of the problem. I decided, I didn't really need a ROM switcher, and sold it. But I did find a Kickfile that allowed me to load a copy of KickStart into RAM, and reset the machine to use 1.3, instead of the 2.04-ROM. Ron.
#74269From: Christopher TolmieOct 22, 1992 9:58 PM
Ron, What is the Kickfile called that loads 1.3 into ram if you have 2.0 ROM installed? I'd like to get a copy of it. chris
#74282From: Ronald B. RomineOct 22, 1992 10:57 PM
Actually, I'm not to sure what it was. I believe it was the ROM image dumped to disk, as a file. It used a command called "Kick13", which would load the KS image into memory, patching(?) it to run at the new location. The machine then resets, using the KS image instead of the 2.04-ROM. There appears to be a commansd called "KickBack, and Reboot", I guess for removing the KickStart image. I downloaded it from a local board. It was a .DMS file, which unpacked to fill a whole disk. All the docs where in French. I found that only two of the files where needed, the Kick13 command, and the KickStart image which was placed in DEVs: To tell the true, I'm not sure as to how legel the file is. I aready own a 1.3-ROM, and users are always coping there ROMs into 32-bit RAM. I'm not worried about the "loading from a file" part. The problem is that the disk already had the KickStart dumped into a file. I don't think KS can be distributed. If it had a comand that dumped the ROM for you, which you could then use — it wouldn't be a problem. :sigh: Ron.
#74326From: Christopher TolmieOct 23, 1992 5:38 PM
Ronald, I too have the 1.3 ROM, but now I'm using 2.04. I was looking for a quick software solution to the ROM switcher. I have one program (a typing tutor) I would like to continue using but it won't run on 2.04. So I thought maybe I could go down the rom version list instead of up like some others do, via software. thanks, Chris