• Please review our updated Terms and Rules here

AlphaMicro Systems AM1000, AM1200, & maybe AM100L drive replacement

I already have two boards, had the developer change the timer interrupt changed to 6 to supersede lower interrupts, got the BIOS and boot rom source code commented, i think i'll leave the CP/M file partition intact and start the AMOSL partition after it (the CD carts have plenty of room) then boot AMOSL from CP/M.

Anyway that's the plan so far.
 
Dope alert, I don't know what a non-bird Cardinal is, was that directed at me classic?
 
That was Alpha Micro's miniaturized USB-based system you could plug into a PC. It used the PC for storage and serial ports, but the processing was done on the USB device (I think a ColdFire CPU). I don't think Birdata makes them anymore and an emulator may be faster anyway, but that doesn't mean they weren't neat.
 
Classic, thanks for the update, they were after my time with Alpha, but i am looking for ward to Mike's emulator.
 
I just wanted to update this thread, I’m now recommending the “Zulu” version of the same scsi2sd card, from the same place, the difference or advantage to the Zulu is no scsi2sd-util because it is built into firmware and runs automatically on power up, nothing to configure, plus to use it as a boot and/or sub drive depends on how you name the image(s) loaded on the SD, HD0.img for the boot drive, HD1(-3).img for sub-drives.


I been using them for over a year now and have come to use them way more than the scsi2sd’s, although once the scsi2sd is setup. It runs as well.

Curbie
 
I just wanted to update this thread, I’m now recommending the “Zulu” version of the same scsi2sd card, from the same place, the difference or advantage to the Zulu is no scsi2sd-util because it is built into firmware and runs automatically on power up, nothing to configure, plus to use it as a boot and/or sub drive depends on how you name the image(s) loaded on the SD, HD0.img for the boot drive, HD1(-3).img for sub-drives.


I been using them for over a year now and have come to use them way more than the scsi2sd’s, although once the scsi2sd is setup. It runs as well.

Curbie
2nd the zuluscsi recommend. Working great in.my am1200.
Update on VAM/L - I'm still in FL so project mostly on hold but working thru the Tom Harte test suite. Anyone know if AM had tests for their
 
2nd the zuluscsi recommend. Works great in.my am1200 (in AK).

Update on VAM/L - I'm still in FL so project mostly on hold but working thru the Tom Harte test suite. Anyone know if AM had their own tests for their 'L' systems?

Related question - the original 'L' systems ran on 68000's but later systems used 010's, 030's and maybe others. My am1200 for example in an 010. Any reason VAM/L should go beyond the base 68000?
 
To my knowledge, the closest thing was SysXser Alpha's system diags.
 
VAM/L - aka 68000 version of VAM for AMOS/L

Quick update for those of you interested in this project.

I'm back in Alaska after a great winter in Florida. Have resumed work on VAM/L.

Finished the "Tom Harte JSON" testing I was working on last fall, VAM/L now correctly runs (in standard 68k mode) all (over a million!) of the tests there.

The AM word kludge is done and seems to work. The clock works. The virtual disk drive, supporting 'container' like volume images, seems to work.

AMOS/L 1.3c starts to come up but is hanging in the first TRMDEF while trying to dump the AM logo stuff to the screen. I think this is a problem in my port of the VAM am300 support code from the WD16 version and hope to resolve it soon.

As you might guess from the above, this is still an 'AM100/L' model, not the 'AM1200' model I ultimately want. So the initial release will probably be something of a hash-up.

BTW - the real machine I'm testing against is a 4meg AM1200 (68010) with a zuluscsi sdcard replacing the original hard disk.

A few things I'm still missing - and hope someone here can help with:

1 - I don't have a 'complete' AMOS/L release to go with it. Closest I've got is the AM1200's 1.3C release that's missing all the .m68 files that should be in the [7,7], [10,1], and [10,2] ppn's. Anyone can share these?

2 - I'm booting the MONTST way, but I don't have any of the ROM's so I'm unsure if that's really the best way. Anyone can share some of these?

3 - Single user mode should be fine so I'm not worrying about the SSD for now. To the extent it proves to be a problem, I expect individual bypasses will be much more productive than any general SSD simulation, but if anyone has information about SSD functionality, I hope they will share it!

More soon when AMOS/L comes up all the way!!
 
VAM/L - aka 68000 version of VAM for AMOS/L

Quick update for those of you interested in this project.

I'm back in Alaska after a great winter in Florida. Have resumed work on VAM/L.

Finished the "Tom Harte JSON" testing I was working on last fall, VAM/L now correctly runs (in standard 68k mode) all (over a million!) of the tests there.

The AM word kludge is done and seems to work. The clock works. The virtual disk drive, supporting 'container' like volume images, seems to work.

AMOS/L 1.3c starts to come up but is hanging in the first TRMDEF while trying to dump the AM logo stuff to the screen. I think this is a problem in my port of the VAM am300 support code from the WD16 version and hope to resolve it soon.

As you might guess from the above, this is still an 'AM100/L' model, not the 'AM1200' model I ultimately want. So the initial release will probably be something of a hash-up.

BTW - the real machine I'm testing against is a 4meg AM1200 (68010) with a zuluscsi sdcard replacing the original hard disk.

A few things I'm still missing - and hope someone here can help with:

1 - I don't have a 'complete' AMOS/L release to go with it. Closest I've got is the AM1200's 1.3C release that's missing all the .m68 files that should be in the [7,7], [10,1], and [10,2] ppn's. Anyone can share these?

2 - I'm booting the MONTST way, but I don't have any of the ROM's so I'm unsure if that's really the best way. Anyone can share some of these?

3 - Single user mode should be fine so I'm not worrying about the SSD for now. To the extent it proves to be a problem, I expect individual bypasses will be much more productive than any general SSD simulation, but if anyone has information about SSD functionality, I hope they will share it!

More soon when AMOS/L comes up all the way!!
Another update: slow progress since my last update. The boot gets thru the full amosl.ini but only using pseudo/null in the trmdef's. My am300 port from the wd16 version is broke; I've decided to spend my time building support for the 6850 ports on the am1200 instead of pounding my head on the am300 wall. While I'm at it I'll try to do the parallel and am1203 & am1213 ports too.

The real am1200 I'm testing with came with a trmdef setup like:
TRMDEF TRM1,AM1200=0:19200,FLPW50,100,100,100
TRMDEF TRM2,AM1200=1:9600,FLP62A,100,200,100
TRMDEF TRM3,AM1200=2:19200,FLP62a,100,200,100
TRMDEF LABEL,AM1213=0:9600,TELTYP,2,2,82
TRMDEF LASER,AM1213=2:19200,TELTYP,2,2,134
TRMDEF RECEIT,AM1213=1:9600,TELTYP,2,2,134
trmdef recei2,am1203=3:9600,teltyp,2,2,134
trmdef trm4,am1203=0:19200,flpw50,100,200,100
trmdef trm5,am1203=1:19200,flpw50,100,200,100
trmdef phone,am1203=2:2400,flp62a,100,200,100
TRMDEF VIDEO,PSEUDO,NULL,40,40,40
;RMDEF FLIP1,FLPIDV,FLPW50,100,100,100
;RMDEF FLP1,FLPIDV,FLPW50,50,50,50
TRMDEF BGP1,PSEUDO,NULL,50,50,50

Looking at this one of the first question that came to mind is: which of these map to which of the dn9 & db25 connectors on the back. Using a modified set of trmdef's:
TRMDEF TRM1,AM1200=0:19200,ANSI,200,200,200
TRMDEF TRM2,AM1200=1:19200,VT100,200,200,200
TRMDEF TRM3,AM1200=2:19200,VT100,200,200,200
TRMDEF TRM4,AM1203=0:19200,VT100,200,200,200
TRMDEF TRM5,AM1203=1:19200,VT100,200,200,200
TRMDEF TRM6,AM1203=2:19200,VT100,200,200,200
TRMDEF TRM7,AM1203=3:19200,VT100,200,200,200
TRMDEF TRM8,AM1213=0:19200,VT100,200,200,200
TRMDEF TRM9,AM1213=1:19200,VT100,200,200,200
TRMDEF TRMA,AM1213=2:19200,VT100,200,200,200

I determined TRM1 thru TRMA map to the connectors as
|1| |2| |3| | ?? | |9| | PP |
|4| |5| |6|
|7| |?|
|?| |?| |?|
where ?, ?? means no output detected
and PP means it's supposed to be a parallel port

So TRM8 & TRM10 didn't (seem to) map to any of the connectors and four of the connectors did not respond to output on any of the trms I defined. All the defined am1200 & am1203 ports seem alive, and one of the am1213 port also

Some questions:
(1) how many ports on an am1200 - From am1200.m68 I'm thinking 0-2. On the other hand even the barest am1200 has one the first line above [1]-[PP}.
(2) how many ports on an am1203 - From the am1203.m68 it looks like 0-3. That seems to match [4]-[7] above.
(3) how may ports on an am1213 - From the am1213.m68 it looks like 0-2.
(4) Anyone have information about the parallel port? I assume it's similar to the parallel port on the am-120, am-100T, and am-100L cards but can find no information on any !of them!

My am1200 emulator doesn't need support for the 1203 or 1213 or even the parallel port initially - but it's something I'd like to add before I call it DONE.
 
My memory matches am1200 0-2, although, I'm confused by this [1]-[PP}
and the 1203 0-3, is the am1213 a db25 4 port board???
 
Oh, I'm a dummy, VFC has done to me also (compressing whitespace I think), and it didn't occur to me.
Is the text graphic and jpg, a db0 pin out?
If you are interested in the pinout, I believe port zero also has a remote reset, if that's what you're interested in, I can check the schematics.
if the am1213 has 4 db25 ports, I believe, there are configuration jumps on the board that define the operation of the ports, serial, parallel, IBM RJE.
 
Back
Top