• Please review our updated Terms and Rules here

AlphaMicro Systems AM1000, AM1200, & maybe AM100L drive replacement

I'm a dummy, I see it now!


..0...1....2
\9/ \9/ \9/ \?/ \?/ \??/
my ascii pic above
line 1: Port numbers
line 2: db pins

I don't recall 6 built-in ports on the am1200 motherboard (I.E. the first line) I'm still confused about the last three ports on the first line.
I'm pretty sure I have some am1200 docs, what should I look for?
 
I have no recollection of that configuration at all, I'll dig through the schematics.
 
Well, I have three sets of schematics for three different revs of 1200's, and am not sure if that covers all 1200's, don't think we ever bought that rev.
At least one schematic say the parallel port runs off a Z80>Z80PIO.

What the first db25 port 4 or the 4th db9 port 4 does I have no clue.
just checked my source library, AM1200.m68 which doesn't seem to have a reference to any other ports than 0,1,or 2, and an AM1213.m68 which references a parallel port and a Z80 DB25 serial port (CP/M?), which still leaves that 4th db9 un-known, hope that's of some help.
 
curbie said:
Well, I have three sets of schematics for three different revs of 1200's, and am not sure if that covers all 1200's, don't think we ever bought that rev.
At least one schematic say the parallel port runs off a Z80>Z80PIO.

What the first db25 port 4 or the 4th db9 port 4 does I have no clue.
just checked my source library, AM1200.m68 which doesn't seem to have a reference to any other ports than 0,1,or 2, and an AM1213.m68 which references a parallel port and a Z80 DB25 serial port (CP/M?), which still leaves that 4th db9 un-known, hope that's of some help.
Click to expand...
i imagine you also have am1203.m68 source...
 
As released by Alpha in 1.1A, looks like standard 68681 Duart stuff.
 

Attachments

  • AM1203.M68.txt
    54.8 KB · Views: 3
nope, 1.1A had it, I don't know about 1.0, I don't know what you're looking for but, is it possible it's a part of the z80 rom stuff, which I don't have?
 
are you writing your VAM/L stuff to emulate at 8/10mhz, or as fast as the host will drive it, or both?
 
curbie said:
nope, 1.1A had it, I don't know about 1.0, I don't know what you're looking for but, is it possible it's a part of the z80 rom stuff, which I don't have?
Click to expand...
What I am really looking for is AM doc showing which of the am1200, am1203, and am1213 ports should map to what connectors on the back
I'm speculating my am1200 has a few faults - wouldn't be surprising on a $200 ebay find!
This has nothing to do with VAM - no reason it needs to match the old real world!
In that same vain I'm not trying to speed match. Even at this early stage, running on a five year old laptop, it's obvious VAM is way faster than my old am1200.
 
I'm not AM documentation, but my guess is; AM1200=0,1,2 are labeled on your pic as db9 (0,1,2); AM1203=db9 (3-10), and AM1213=0,1,2 db25 (3), db9 (4), db25 (5).
Now if the AM1213 ports are like the AM1013 ports, there are also jumpers to configere the port's function.

One of the first things I did for FMC was to setup 1013's IBM RJE PORT to send their customers Medicare charges to Blue Cross/Blue Shield, so if your 1213 is not .jumpered for 3 serial ports, that would be an issue, if I recall correctly and if the 1203 functions the same as the 1013.
 
Another update on VAM/am1200 progress. Definitely not ready to upload but working well enough I've put away my real am1200 & doing the rest of the development using just the emulator.
It boots all the images I have (1.3, 1.3c, 2.3a). VUE, FIX, BASIC, GCC all work as does most else.
DATE & TIME both work synced to host date/time. Speaking of host(s), it run on fedora linux 40, WSL on Windows 10, Cygwin on Window 10, and Termux on my Samsung phone & tablets.
Performance on my window laptop is about 10 times that of real am1200 as measured by using GCC to compile for.c[7,45] - about 1 minute on the real box, 5 seconds on the emulator.
What's not working?
- no monitor echo of typed chars, but telnet does work and setting my telnet client to local echo is a temporary fix.
- As above the clock 'works', but that's 'cause the gdate/gtime svc's are being intercepted. The port emulation is not there yet.
- Timer barely functional, Stuff that needs better still does not work.
- Real serial port I/O still not right. Using what I call 'fake io' instead. Intercepting terminal services calls to get around that for now.
I consider all the above 'must fix' before I can let it out the door. I hoped to have an alpha release out by month end however that's gonna slip some. Still - SOON!
 
I'm keeping an eye on VAM's release, not pushing just keeping an eye here for an announcement.
Will also run on linux?

good luck,
curbie
 
I am seeking to learn if AlphaMicro or any successor in interest would object to my internet posting of their AMOS/L (68000 based) software and/or documentation. I am aware many sites (for example bitsavers.org) have posted that documentation but have not discovered sites posting that software.

AlphaMicro has in the past explicitly allowed me to post older version of their software and documentation, However they have, for several years, not responded to my inquiries regarding extension of that permission. Their website (alphamicro.com) has long been seriously broken. It was apparently last updated over ten years ago and few links work at all; "contact" is not one of the working ones.

It is my belief AlphaMicro is no longer in business and that no successor in interest exists or cares about this matter. I have spoken to many about this and no one has contradicted my belief.

If you claim any interest in this matter or know of any party that does please inform me as soon as possible. First posted 5/22/2024. You may reach me at mikenoel37@gmail.com.
 
Mike,

Would you please let me know of any claims. Last i heard Alpha's corps was sold to a big alpha dealer for $40k.
 
FYI, regarding Alphamicro's continued existence, I heard back from alphamicro/birmingham as indicated below:

Alpha Microsystems <info@alphamicro.com>

Mike:
Thank you for your inquiry.
Alpha Micro is functioning, with the current mission to support those end users with their Alpha Micro hardware and software support needs, and to replace their aging Alpha Micro servers with new Alpha Micro servers.
Alpha Micro works closely with Birmingham Data Systems, and other dealers, to meet their end user needs.
Please feel free to provide us information about your interest in Alpha Micro and your interests with regards to Alpha Micro products.
Thank you !
Info @ Alphamicro.com

Mike Noel <mikenoel37@gmail.com>

OK, What's your name and what is your connection to AlphaMicro and/or Birmingham Data Systems?
It is my understanding both those entities are out of business without succesor.
If this is not the case please provide evidence including current, verifiable contact information. Best, Mike

Alpha Microsystems <info@alphamicro.com>

Mike:
Most of the Alpha Micro hardware, software, and AMOS licensing sales are originating through Birmingham Data Systems, who is authorized to sell Alpha Micro hardware, software, and licensing products. This has been the case for nearly 25 years, and continues to be the case.
Birmingham Data Systems has numerous Alpha Micro users, which are regularly supported by BDS as needed.
A working phone number for BDS is 248-802-6409.
Thank you for your inquiry.
Info@alphamicro.com

Mike Noel <mikenoel37@gmail.com>

0k, Despite lack of a name in your response you've convinced me some remnent of Alphamicro is still in business so I will refrain from publishing Alphamicro software. I will instead list your email & phone number as contact for anyone desiring to license it for use with my 68000 emulator. Honestly, I think most hobbiests already posses copies from their own hardware. Best, Mike
 
Since it appear posting Alphamicro software is a NoGo I will need to modify my emulator to customize existing installations "on the fly" rather than posting installations already customized for it. My plan for this is
- utilize my existing boot time MONGEN feature to load my disk driver into the DSK0: monitor, but instead of getting the driver from DVR: getting the driver from the host environment
- intercept the first FETCH following boot, which should be for AMOSL.INI
- feed the monitor a simple customized AMOSL.INI from the host environment instead of from the existing DSK0:
This sounds pretty easy but I haven't started work on it yet. Obviously it will delay my release of the emulator at least a few weeks.
 
You must log in or register to reply here.
Back
Top