Yahoo Groups archive

Emax

Index last updated: 2026-04-28 23:23 UTC

Thread

Q's and A's about Emax 1 internal hard drives

Q's and A's about Emax 1 internal hard drives

2003-02-16 by Vir Cotto <s.savisaari@...>

Hi, new member here.
I spent an hour yesterday reading old posts concerning the make and 
type of a suitable hard disk replacement for Emax 1 HD. I simply took 
an 40 MB IBM-made SCSI drive from an ancient Macintosh SE, hooked it 
on and used the "Burn in HD" command in the diagnostics menu. It's 
only formatted as a 20 MB drive, obviously, and it's been working 
flawlessly for 4 years now. No problem at all.
Well.. you probably knew this already. Just a comment.

V.C.

Re: [emax] Q's and A's about Emax 1 internal hard drives

2003-02-16 by John Silveria

Thanks for the info. Using old mac classic compatible parts (hard drives, CD-Rom 
drives, Floppy drives) is a very good way of finding compatible parts.

On 16 Feb 2003 at 10:41, Vir Cotto s.savisaari@... spoke unto me:

> Hi, new member here.
> I spent an hour yesterday reading old posts concerning the make and
> type of a suitable hard disk replacement for Emax 1 HD. I simply took
> an 40 MB IBM-made SCSI drive from an ancient Macintosh SE, hooked it
> on and used the "Burn in HD" command in the diagnostics menu. It's
> only formatted as a 20 MB drive, obviously, and it's been working
> flawlessly for 4 years now. No problem at all. Well.. you probably
> knew this already. Just a comment.
> 
> V.C.
> 
> 
> Emax and Emax II User's Group Website
> 
> http://www.silveriafamily.com 
> 
> Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/ 
> 
> 



**************************John Silveria II****************************
                   AIM & Yahoo! Messenger: EmaxJS
                        MSN: emaxjs@...
The Silveria Family Website & Emax and Emax II User's Group
------------------ http://www.silveriafamily.com ----------------------

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.