The Chipmunk PCB plugs into the M100 system bus connector (like the DVI) and a long thin ribbon exits, much like the DVI cable, between the M100 and the ROM Bank. The ROM Bank plugs into the Option ROM socket. Only Disk+ (1) and SuperROM (2) are in the ROM Bank. The ROM Bank has a rotary switch to select a ROM (1-6): Turn off M100, select a ROM (1 or 2) with the rotary switch, and turn on the M100. No Reset needed. The last used ROM (DISK+ or SUPER) will still be listed in the M100 menu, but the now selected ROM will be activated when the other is chosen from the M100 Menu. Upon exit the M100 Menu will be changed to show the latest/active ROM. A bit confusing, but all is explained in the ROMBank manual.
As for the location of the Chipmunk ROM, probably a two parter between the drive and the PCB; e.g. if the Chipmunk works as a host similar to the DVI or TPDD 1/2. Otherwise, your guess as good as mine. God bless, GregS <>< Mar 1, 2022 6:34:51 AM Brian White <b.kenyo...@gmail.com>: > When you say cdos rom, do you mean that you have an option rom that has cdos > on it? Or do you mean a rom in the drive? > > If you have an option rom, then it will almost certainly be installed the > same way as any other option rom. CALL 63012 (or 63012,1 or 63013 or > 63013,1). > > The reset or CALL0 directions are for triggering the drive to install cdos in > ram from a disk via the bus connection like the Disk/Video Interface does. > call0 is supposed to be more bulletproof because reset doesn't necessarily > install, it just checks a flag in ram to see if it needs to install, and that > could be wrong if memory or an installed cdos got corrupted. > > But if you have a rom, then you have a rom. That will take the place of the > normal way. It probably does still install ram components, because I believe > cdos modifies BASIC and TELCOM etc, but that doesn't change how any option > rom is activated. The initial kick off will be by activating that rom, which > will be the same as any other. > > The only difference will be that you also have a rom expander in the mix. So > first you will have to know how to operate the expander to select different > roms and activate them and switch between them, THEN do that to select the > cdos rom. > > Myself, since I have all the stuff and it would be convenient, I would start > by removing variables by starting without the rom expander and moving the > cdos rom from the expander to the m100 directly. Temporarily just to remove > variables and figure out one thing at a time. > > Those expanders usually have some rom sockets that are like the m100 and some > that are standard. > > If the cdos rom happens to be fitted with a pinout adapter and installed in a > molex socket like what the m100 has, then it's easy, just remove the expander > and pop the cdos rom directly in the m100 and CALL 63012. > > If the cdos rom is a standard eprom without a pinout adapter and installed in > a standard dip-28 socket, Then you'd need an eprom programner and a rex or > teeprom to try to use the rom by itself without the expandet. So in that case > just make sure you've mastered the expander first by loading and switching > between other roms before trying the same with cdos. > > And just bear in mind the possibility that the cdos manual may be slightly > wrong in your case, since it may only describe the normal disk-based install > method and your rom may be taking the place of part of that. You probably > don't need any reset or CALL0. > > I have a Sardine rom in a PG Designs / Tavelling Software expander that's > like that. The manual only describes the normal disk install method. The > expander has it's own special directions for installing that version of > Sardine. In that case those directions were essentially to select rom slot #5 > in the expander and launch that rom the same as any other rom. 'select #5' in > that case meant to execute a BASIC instruction or two which affects the > expander. I think the pcsg expander has a thumb wheel? > > -- > bkw > > On Mon, Feb 28, 2022, 8:18 PM Greg Swallow <gswal...@mchsi.com> wrote: >> I have a PDF of the manual and as best I can figure the included Chipmunk >> power supply is around the same current as the M100 PS as the M100 PS will >> power the drive, but it will not properly charge the Chipmunk battery. The >> manual even notes the Chipmunk PS should not be used to power the M100 as >> the Chipmunk PS is 1.5 volts greater (7.5VDC) than the M100 PS (6VDC) and >> the Chipmunk PS would certainly damage the M100. Some pictures show a >> Chipmunk with a 7.5VDC 400ma PS. The Chipmunk takes a 5.5mm OD x 2.1mm ID >> plug with a Negative (-) center. The PS I have (DMD-8201500) is adjustable >> up to 24VDC with a max of 1.5A. It does not have a breakdown of amps vs VDC >> or anything about watts/power. So I am unsure if current at 7.5VDC is the >> same/less than at 24VDC. >> >> When I turn everything on and RESET (hard/soft) the M100 the Chipmunk lights >> up as if a boot process is attempting to find something. The CDOS Menu does >> not appear and the M100 goes on unaware of the process. I thought I read >> somewhere that the CDOS ROM can be run with a CALL 0 from BASIC, but this >> has done nothing that I can note. There is evidently a RAM portion of CDOS >> and I am hoping this is what the Chipmunk is trying to find on the drive. >> Possibly the CDOS ROM is like a BIOS and needs something from the CDOS >> Utility disk to complete the process of loading CDOS Menu to RAM. Once >> loaded, the CDOS Menu, can be turned On/Off in a similar fashion as TS-DOS. >> >> Thanks for the help y’all. I will check out the M100SIG files and see if I >> can find more clues. >> >> >> God Bless, >> >> GregS <>< >> >> >>> On Feb 28, 2022, at 4:11 PM, Brian K. White <b.kenyo...@gmail.com> wrote: >>> >>> On 2/28/22 17:51, Brian K. White wrote: >>>> I have a manual for the chipmunk drive I can scan. >>> >>> Also there's a bunch of info in the M100SIG >>> https://github.com/LivingM100SIG/Living_M100SIG/blob/main/M100SIG/Lib-09-PERIFERALS/CHIPMK.CAT >>> No disk image though. >>> >>> -- >>> bkw >>> >>
