[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Hardware Project

Subject: Re: Hardware Project
From: david@uow.edu.au (David Wilson)
Date: 1998/11/12
Newsgroups: comp.sys.apple2
Organization: University of Wollongong, Australia
References: <364919f0.0@news.cgocable.net> <364A6F6E.46D6C5B6@thegrid.net> <david.910851756@wraith> <Pine.GSO.3.96.981112082457.18971F-100000@ordinateur>

Will Smith <root@ordinateur.ctron.com> writes:

>On 12 Nov 1998, David Wilson wrote:

>> Disadvantages:
>> 	I never bothered to upgrade it to v2.x as I would have to
>> 	program another EPROM - if I built this again today I might use
>> 	EEPROM or Flash memory to ease the upgrading.

>i don't know much about EEPROMs.  if a patch needed to be done on an OS on
>the EEPROM, could it be done?

An EEPROM can be electrically erased. Thus, with an appropriate driver an
EEPROMdisk card could support the WRITE and FORMAT calls as well as the
READ & STATUS ones. EEPROMs can have a limited number of writes and may
not be able to erase single bytes (just blocks) and are much slower to
write than to read. None of these would cause problems in this situation.
--
David Wilson  School of IT & CS, Uni of Wollongong, Australia  david@uow.edu.au

References:
- Hardware Project
  - From: "Terence J. Boldt" <apple2@cgocable.net>
- Re: Hardware Project
  - From: Cap Weir <cap@thegrid.net>
- Re: Hardware Project
  - From: david@uow.edu.au (David Wilson)
- Re: Hardware Project
  - From: Will Smith <root@ordinateur.ctron.com>

Prev by Date: Re: Help!! Trying to print to a printer on NT server from Mac
Next by Date: PC transporter drives
Previous by thread: Re: Hardware Project
Next by thread: Re: Hardware Project
Index(es):
- Date
- Thread