• Please review our updated Terms and Rules here

AlphaMicro Systems AM1000, AM1200, & maybe AM100L drive replacement

ok Mike, my inclination is, that original drive is a SASI 70MC as listed in FIX420 (the drive and the AMOSL.MON the image is made from), the driver trying to boot the image and AMOSL.MON is a SCSI device, the boot proms are looking for a SASI and a AMOSL.MON that has a SASI driver in it.
 
The label(s) on the hard drive say Micropolis 1375 170mb SCSI. The extracted image contains 5 28mb partitions (DSK0-DSK4). Given this original drive is SCSI, why would the boot roms and system disk driver be for a SASI drive; and why would they work with that original SCSI hard drive drive and not with the emulated SCSI drive?
I'm more inclined to think my novascsi config is bad...
 
I'm sorry Mike, that drive looks exactly like 70MC, and the SASI era was more my time, I'm not sure about SCSI drivers I wrote a bunch .DVRs and .IDVs for SASI.
from my understanding you sound correct about the boot proms looking for a SCSI device and if AMOSL.MON was being found on the Micropolis, it should AMOSL.MON on the SCSI2SD.

My guess is, the SCSI driver queries the device, then builds a driver from those queried parameters in monitor memory.

Before the SCSI2SD, I was most scared of losing the AMOSL/AMOSL32 OS, the very first thing I did after getting the SCSI2SD up and running was make a bootable SD, imaged it, and saved it on my linux system, I now have several images and many backups of them. The thing I like these images is I can .ZIP them down and email them to people with real email accounts.
 
curbie said:
I'm sorry Mike, that drive looks exactly like 70MC, and the SASI era was more my time, I'm not sure about SCSI drivers I wrote a bunch .DVRs and .IDVs for SASI.
from my understanding you sound correct about the boot proms looking for a SCSI device and if AMOSL.MON was being found on the Micropolis, it should AMOSL.MON on the SCSI2SD.

My guess is, the SCSI driver queries the device, then builds a driver from those queried parameters in monitor memory.

Before the SCSI2SD, I was most scared of losing the AMOSL/AMOSL32 OS, the very first thing I did after getting the SCSI2SD up and running was make a bootable SD, imaged it, and saved it on my linux system, I now have several images and many backups of them. The thing I like these images is I can .ZIP them down and email them to people with real email accounts.
Click to expand...
FINALLY got the am1200 to boot from the zuluscsi! Was tearing my hair out, turns out the problem was a bad switch on the zuluscsi card. Was supposed to be "no termination", but was going the other way. Ran the switch back & forth a few times & now it boots like a rocket.
I pulled the old HD out, perm installed the zuluscsi, disconnected the old (incredibly noisy) fan and am now running it without a fan. Any thoughts on likelihood of overheating? Seems fine in the short ~hour runs so far, but thinking it's worth installing a new (quieter!) one.
 
Chalk up another one, those Zulu cards are quickly becoming my recommendation. Do you suppose one could copy a amos-x.x-container image onto a SD card, rename it to HD1.IMG sub-drive, then read it using a AMOSL machine?
 
curbie said:
Chalk up another one, those Zulu cards are quickly becoming my recommendation. Do you suppose one could copy a amos-x.x-container image onto a SD card, rename it to HD1.IMG sub-drive, then read it using a AMOSL machine?
Click to expand...
I suppose one could. There would be AMOSL.INI mods to accomate the 2nd (3rd, 4th) image. I expect I'll be doing that shortly to get some of my am1000 stuff & the C distro over.
Zulu also supports tape and cd simulation - I'd like to get those working too, but
May have to wait on those as I want to pivot to getting VAM/L out before I head south for the winter.
 
Thanks Mike,

I get a lot of people contacting me, looking for solutions so it's helpful to not chase my tail too much.
If you run into any AMOSL Ver 1.0 or 1.1A OSs I'm interested in copies.
Just got one of my eagles up and running, starting on the other one today.
 
curbie said:
Thanks Mike,

I get a lot of people contacting me, looking for solutions so it's helpful to not chase my tail too much.
If you run into any AMOSL Ver 1.0 or 1.1A OSs I'm interested in copies.
Just got one of my eagles up and running, starting on the other one today.
Click to expand...
I've a 1.0b system from my 80's am1000. Been firing it up on the am1200. Will let you know when I have a good image available.
The 1200 is 1.3c, which, based on a amos.dir[1,2] file I found on it seems missing the [7,7] .m68's for the .unv's; also the whole [10,1] ppn and much of the [10,2] ppn. Do you have a complete 1.3c image?
 
Yes, I have 1.2, 1.3c, 1,4d, 2.3 calc, write, esp, dart, sv,... I'm currently setting up an eagle with to zulu cards, when that's done, i should be able to trade for anything listed that you need.
 
i use amos.dir for proper files by name, but upgrades have buggered verify on hash and versions.
 
mike,

i have or will have a complete or near complete 1.3c os, built form a couple of oss, based on their amos.dir files, not quite sure where i left off, this has been an on-going project, trying to rebuild my icm system which included current source code, something to do in retirement.
 
mikenoel37 said:
FINALLY got the am1200 to boot from the zuluscsi! Was tearing my hair out, turns out the problem was a bad switch on the zuluscsi card. Was supposed to be "no termination", but was going the other way. Ran the switch back & forth a few times & now it boots like a rocket.
I pulled the old HD out, perm installed the zuluscsi, disconnected the old (incredibly noisy) fan and am now running it without a fan. Any thoughts on likelihood of overheating? Seems fine in the short ~hour runs so far, but thinking it's worth installing a new (quieter!) one.
Click to expand...
Replying to my own post! Replaced the noisy old fan with this drip in https://www.amazon.com/dp/B009OXTWZI?ref=ppx_pop_mob_ap_share
28 db job. Keeps case (wo old HD!) nice & cool, almost inaudible.
On another note - does anyone have source (.m68) for a non-interrupt (clock queue) Idv? I seem to recall when the 100L came out there were such drivers for the PS3 & DCH cards but cant find one now. For vam/l testing...
 
curbie said:
Chalk up another one, those Zulu cards are quickly becoming my recommendation. Do you suppose one could copy a amos-x.x-container image onto a SD card, rename it to HD1.IMG sub-drive, then read it using a AMOSL machine?
Click to expand...
2nd reply - just realized you were asking about AMOS (not L) images mounted in a sub. I've AMOS 4.6, 5.0 and Alpha Accounting (& some of my other wd16 stuff) from VAM setup on a zuluscsi sd image & it works fine as amosl subsys.
 
Mike,

M68 for what non-interrupt (clock queue) . IDV?
I also have Alpha Accounting source code, but I do have people asking for AMOS OSs.
 
Is "HD1_wd16amos.hda" what I'm looking for 1.2, qans is it readable as HD1.IMG with a Zulu?
 
Thanks, I'm rebuilding a disk structure for someone, but will dig into this after that.

Do you have 1.1a or 1.0? I think I can assemble a good chunk of 1.1a from source code, but am still looking for a complete OS.
 
curbie said:
Thanks, I'm rebuilding a disk structure for someone, but will dig into this after that.

Do you have 1.1a or 1.0? I think I can assemble a good chunk of 1.1a from source code, but am still looking for a complete OS.
Click to expand...
I had thought my old am1000 image was 1.0x but from what I've recently found it MAY be much newer (1.3x?). At least that's what dir/v implies. But it is early enough it does not have SSD "support", nor the power on copyright notice.
 
You must log in or register to reply here.
Back
Top