Image Map Image Map
Page 1 of 3 123 LastLast
Results 1 to 10 of 27

Thread: Alpha Micro 1000

  1. #1

    Default Alpha Micro 1000

    Does anybody else have one of these?

    http://www.old-computers.com/museum/...asp?c=606&st=1

    Its been a pretty cool machine to play with. Mine has two hard drive in it. Unfortunately, one of the hard drives is dying. When I try tapping into different areas of the system, it'll just not work. Occasionally I can get it to work if I keep trying.

    Here's the bad part... the AMOS OS was pre-installed by the company before they shipped the machine which means that installation disks are rare to non-existent.

  2. #2

    Default

    Pretty much impossible to get any AMOS installation media. Alpha Micro existed until recently and sold the install media ("AlphaCD") for several hundred bucks. In theory they still exist today, but since their website is hacked and Viagra ads all over i guess they are "Not so active any more"....

    http://www.alphamicro.com/

    Originally you made backups on an old NTSC VCR (No joke!). But since these HDDs are normal SCSI-1 you should try to make backups in a different machine asap. Maybe the usual tricks work to backup the files - place the drive sideways or upside down. If that fails then maybe something like unstoppable copier:

    http://www.roadkil.net/program.php?ProgramID=29

    depending on the type of failure it might even be possible to replace the electronics or chassis from a working drive of the same type.

  3. #3
    Join Date
    Oct 2008
    Location
    Kamloops, BC, Canada
    Posts
    6,252
    Blog Entries
    44

    Default

    OH hey!
    One of those machines were on ebay last week.
    [Need something to waste time on? Click here to visit my YouTube channel CelGenStudios]
    --------------------------------------------------------------------------------------------
    [No time for videos? Click here to visit my Twitter feed @CelGenStudios]

    = Excellent space heater

  4. #4

    Default

    I've got an Alpha Micro Eagle 300, among other systems. It serves its own website:

    http://ampm.floodgap.com/

    AMOS is a special OS to me because it was the first one I ever broke into (long story there). The AM-1000 is a solid machine but yes, the hard disks in those seem to die if you look at them funny. Do you have a floppy drive in it? You may be able to make a boot disk off it.

    Unfortunately, I've never seen an AM-1000 that was true SCSI: they're either SASI or ST-506. It might work if you load it into a cloning station though.
    I use my C128 because I am an ornery, stubborn, retro grouch. -- Bob Masse
    Various projects and oddities: http://oldvcr.blogspot.com/
    Machine room: http://www.floodgap.com/etc/machines.html

  5. #5

    Default

    I believe there's two ST-506s in it,but there's no floppy drive. It boots up fine, but it gets cranky if I try to access certain parts of the data. I'm not really sure how the drives are laid out in it with regards to data and the OS. I downloaded the AMOS OS instruction manual a while ago. This machine used to be located in a pharmacy. I got it to give me the access code for the pharmacy's safe once, but I think that part of the disk is no longer accessible.

    I could attempt to build a cloning station, although I've never made one in my life

  6. #6

    Default

    I pulled up one of my logs from it. This is what I'm getting. I'm pretty sure these errors are on the drive solely for storage. Forgive me, it's been a while since I pulled it out and played with it...

    Code:
    ? PHARM ?
    .dsk0[377,0]pharm.cmd
    ?File specification error 
    .dsk0:[377.0]pharm.cmd
    %Warning -- Program is not reusable
    ?Disk error type 1, code 2 on    0:, physical block 27577
    ?Disk error type 1, code 5 on    0:, physical block 40103
    ?Disk error type 1, code 2 on    0:, physical block 1
    ?Disk error type 1, code 5 on    0:, physical block 1
    ?Disk error type 1, code 5 on    0:, physical block 1
    ?Disk error type 1, code 5 on    0:, physical block 1
    ?Disk error type 1, code 5 on    0:, physical block 1
    ?Disk error type 1, code 5 on    0:, physical block 1
    ?Disk error type 1, code 5 on    0:, physical block 1
    ?Disk error type 1, code 5 on    0:, physical block 1
    ?Disk error type 1, code 5 on    0:, physical block 1
    ?Disk error type 1, code 5 on    0:, physical block 1
    ?Disk error type 1, code 5 on    0:, physical block 1
    ?Disk error type 1, code 5 on    0:, physical block 1
    ?Disk error type 1, code 5 on    0:, physical block 1
    ?Disk error type 1, code 5 on    0:, physical block 1
    ?Disk error type 1, code 5 on    0:, physical block 1
    ?Disk error type 1, code 5 on    0:, physical block 1
    ?Disk error type 1, code 5 on    0:, physical block 1
    ?Disk error type 1, code 5 on    0:, physical block 1
    ?Disk error type 1, code 5 on    0:, physical block 1
    ?Disk error type 1, code 5 on    0:, physical block 1
    ?Disk error type 1, code 5 on    0:, physical block 1
    ?Disk error type 1, code 5 on    0:, physical block 1
    ?Disk error type 1, code 5 on    0:, physical block 1
    ?Disk error type 1, code 5 on    0:, physical block 1
    ?Disk error type 1, code 5 on    0:, physical block 1
    ?Disk error type 1, code 5 on    0:, physical block 1
    ?Disk error type 1, code 5 on    0:, physical block 1
    ?Disk error type 1, code 5 on    0:, physical block 1
    ?Disk error type 1, code 5 on    0:, physical block 1
    ?Disk error type 1, code 5 on    0:, physical block 1
    ?Disk error type 1, code 5 on    0:, physical block 1
    ?Insufficient memory to load program PH0100.RUN
    .dsk:[377,0]cdir
    ?Disk error type 1, code 5 on DSK0:, physical block 2
    ?Cannot read DSK:CDIR.LIT - device not ready 
    ?Disk error type 1, code 5 on DSK0:, physical block 2
    ?Cannot read DSK:CDIR.CMD - device not ready 
    ?DSK:[377,0]CDIR?
    .type dsk0:[stdfmt.txt
    ?Disk error type 1, code 5 on DSK0:, physical block 173
    ?Cannot read DSK0:TYPE.LIT[1,4] - device not ready 
    ?Disk error type 1, code 5 on DSK0:, physical block 4652
    ?Cannot read DSK0:TYPE.CMD[2,2] - device not ready 
    ?Disk error type 1, code 5 on    0:, physical block 2
    ?Cannot read TYPE.LIT - device not ready 
    ?Disk error type 1, code 5 on    0:, physical block 2
    ?Cannot read TYPE.CMD - device not ready 
    ?Disk error type 1, code 5 on    0:, physical block 2
    ?Cannot read TYPE.LIT - device not ready 
    ?Disk error type 1, code 5 on    0:, physical block 2
    ?Cannot read TYPE.CMD - device not ready 
    ?Disk error type 1, code 5 on DSK0:, physical block 173
    ?Cannot read DSK0:MDO.LIT[1,4] - device not ready 
    ?TYPE?
    .type dsk0:[
    ?Disk error type 1, code 5 on DSK0:, physical block 173
    ?Cannot read DSK0:TYPE.LIT[1,4] - device not ready 
    ?Disk error type 1, code 5 on DSK0:, physical block 4652
    ?Cannot read DSK0:TYPE.CMD[2,2] - device not ready 
    ?Disk error type 1, code 5 on    0:, physical block 2
    ?Cannot read TYPE.LIT - device not ready 
    ?Disk error type 1, code 5 on    0:, physical block 2
    ?Cannot read TYPE.CMD - device not ready 
    ?Disk error type 1, code 5 on    0:, physical block 2
    ?Cannot read TYPE.LIT - device not ready 
    ?Disk error type 1, code 5 on    0:, physical block 2
    ?Cannot read TYPE.CMD - device not ready 
    ?Disk error type 1, code 5 on DSK0:, physical block 173
    ?Cannot read DSK0:MDO.LIT[1,4] - device not ready 
    ?TYPE?
    .type dsk1:[100,0
    ?Disk error type 1, code 5 on DSK0:, physical block 173
    ?Cannot read DSK0:TYPE.LIT[1,4] - device not ready 
    ?Disk error type 1, code 5 on DSK0:, physical block 4652
    ?Cannot read DSK0:TYPE.CMD[2,2] - device not ready 
    ?Disk error type 1, code 5 on    0:, physical block 2
    ?Cannot read TYPE.LIT - device not ready 
    ?Disk error type 1, code 5 on    0:, physical block 2
    ?Cannot read TYPE.CMD - device not ready 
    ?Disk error type 1, code 5 on    0:, physical block 2
    ?Cannot read TYPE.LIT - device not ready 
    ?Disk error type 1, code 5 on    0:, physical block 2
    ?Cannot read TYPE.CMD - device not ready 
    ?Disk error type 1, code 5 on DSK0:, physical block 173
    ?Cannot read DSK0:MDO.LIT[1,4] - device not ready 
    ?TYPE?
    .

  7. #7

    Default

    Yup, bad disk. I'm having trouble determining what you're trying to type, though. To move from PPN to PPN, use the LOG command (such as LOG OPR:, which should put you into the operator account, assuming there's no password lock on it).
    I use my C128 because I am an ornery, stubborn, retro grouch. -- Bob Masse
    Various projects and oddities: http://oldvcr.blogspot.com/
    Machine room: http://www.floodgap.com/etc/machines.html

  8. #8

    Default

    I think I was trying to run "pharm.cmd" and it just crapped out at that point. What's PPN? Forgive me, I'm not all that fluent in AMOS. The thing is currently sitting in storage, and I was thinking of taking it out for another spin.

  9. #9

    Default

    Quote Originally Posted by ClassicHasClass View Post
    I've got an Alpha Micro Eagle 300, among other systems. It serves its own website:

    http://ampm.floodgap.com/

    AMOS is a special OS to me because it was the first one I ever broke into (long story there). The AM-1000 is a solid machine but yes, the hard disks in those seem to die if you look at them funny. Do you have a floppy drive in it? You may be able to make a boot disk off it.

    Unfortunately, I've never seen an AM-1000 that was true SCSI: they're either SASI or ST-506. It might work if you load it into a cloning station though.

    Do you have AMOS 2.3a? Afaik that was the last AMOS that supported the 68k processors and probably the one that is most fun on an AM-1000... Unfortunately there is not even a youtube video about AMOS, i think best i could find were 2 or 3 screenshots, it's THAT rare. If you have any installation media then please make some backups, maybe you'll one day be the hero to preserve it for future generations...


    On a side-note: SASI is a subset of SCSI-1, so SASI controllers "should" be SCSI-1 compatible afaik. I think some ST-506 Harddisks were even sold as SCSI - these just had an adaptor/converter thingy attached.
    Last edited by kyodai; October 17th, 2015 at 08:05 AM.

  10. #10

    Default

    I have AMOS, but on CD (I have the AlphaCD) -- I don't have VHS media for it. As a result, my workhorse Alpha Micro systems are later CD-ROM equipped models (the E300 and an E100 backup).

    I know SASI is a strict subset of SCSI-1, but I've heard of SASI devices doing weird things when connected to SCSI controllers, even old ones. Yes, there were some ST-506 drives that were aftermarket conversions to SCSI but just with an active interposer board or some such.

    What's PPN?
    A PPN is a project-programmer number, expressed in octal, ranging from [0,0] to [377,377] (however, AMOS does not seem to support project 0, so PPNs start at 1,0). This is a DEC-ism which was carried over. Here's a quick primer to AMOS: http://ampm.floodgap.com/www/amos.htm

    This would get annoying for common locations, so AMOS allows ersatzes which are aliases. OPR: is an alias for DSK0:[1,2].
    I use my C128 because I am an ornery, stubborn, retro grouch. -- Bob Masse
    Various projects and oddities: http://oldvcr.blogspot.com/
    Machine room: http://www.floodgap.com/etc/machines.html

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •