2068 ROM Sources
16 messages · 2004-03-13 → 2004-08-03 · Yahoo Group era · View archive on archive.org
Participants: aralbrec, Jeff Burrell, Jeff, Jarek Adamski, Jack Boatwright, Don Dindang, Bill aka OhnO the Clown, rafael_mnrq
Preserved from the Timex/Sinclair 2068 Yahoo Group (2001–2019), which is no longer online. Text reproduced from the archive.org archive; email addresses masked.
Messages
1. 2068 ROM Sources
Jeff · Sat, 13 Mar 2004 21:19
I have posted a set of sources for the Home and Extension Roms in the
"FILES" area. I am sorry that it has taken so long, but I wanted to
put them into a format usable by a PD assembler. I have chosen the
assembler that is included with the Z88DK since it is readily
available from Source Forge. It took a little more time than I
thought to massage the Cross32 files since the Z88DK assembler doesn't
have macro capabilities.
At any rate, I have assembled the modified files and have gotten a
byte-for-byte match with the ROM binaries from the web.
Enjoy
2. Re: 2068 ROM Sources
aralbrec · Fri, 11 Jun 2004 08:21
--- In [email], "Jeff" <jburrell7@y...> wrote:
> I have posted a set of sources for the Home and Extension Roms in
the
> "FILES" area. I am sorry that it has taken so long, but I wanted to
> At any rate, I have assembled the modified files and have gotten a
> byte-for-byte match with the ROM binaries from the web.
Nice work Jeff :-)
Now I suggest a mini-project. There is currently
no convenient means to preserve ts2068 cartridge
software. There is also some demand for diagnostic
software that can help troubleshoot a malfunctioning
computer. So my thought is adding a menu that can be
activated at power up if certain keys are pressed.
One option in the menu would dump the contents of
the dock bank (maybe to tape?) so we can make
cartridge images. Another option would run some
diagnostics to help identify hardware problems
(this would need to have audio as well as visual
feedback since most often a bad 2068 = no display).
There is a lot of spare room in the EXROM for
even a significant program, though these mods would
be minor.
I think most people are reluctant to make mods
to their hardware so the best bet is probably to
put an EPROM on a small daughterboard that can be
plugged into the EXROM socket.
Alvin
3. Re: [ts2068] Re: 2068 ROM Sources
Jeff Burrell · Sun, 13 Jun 2004 10:30
After examining the 2068 schematics, it would seem that a small board that plugs onto the rear expansion could do the trick. You would remove the EXROM from the motherbord and then plug the expansion board with a new EXROM onto the 2068. This would allow for use of a flash with a full 64K of available memory. I would be partial to having at least one high speed (116Kb or more) RS-232 link to allow communication with a PC. This would allow for display and control of the diagnostics as well as upload of any dock bank devices.
This method should cover 90%+ of all machines because if a 2068 is so sick that it can't even get to the EXROM, you are at the point where scope and logic analyzer are needed.
What say you?
aralbrec <[email]> wrote:
--- In [email], "Jeff" <jburrell7@y...> wrote:
> I have posted a set of sources for the Home and Extension Roms in
the
> "FILES" area. I am sorry that it has taken so long, but I wanted to
> At any rate, I have assembled the modified files and have gotten a
> byte-for-byte match with the ROM binaries from the web.
Nice work Jeff :-)
Now I suggest a mini-project. There is currently
no convenient means to preserve ts2068 cartridge
software. There is also some demand for diagnostic
software that can help troubleshoot a malfunctioning
computer. So my thought is adding a menu that can be
activated at power up if certain keys are pressed.
One option in the menu would dump the contents of
the dock bank (maybe to tape?) so we can make
cartridge images. Another option would run some
diagnostics to help identify hardware problems
(this would need to have audio as well as visual
feedback since most often a bad 2068 = no display).
There is a lot of spare room in the EXROM for
even a significant program, though these mods would
be minor.
I think most people are reluctant to make mods
to their hardware so the best bet is probably to
put an EPROM on a small daughterboard that can be
plugged into the EXROM socket.
Alvin
Yahoo! Groups SponsorADVERTISEMENT
---------------------------------
Yahoo! Groups Links
To visit your group on the web, go to:
http://groups.yahoo.com/group/ts2068/
To unsubscribe from this group, send an email to:
[email]
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
---------------------------------
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger
4. Re: 2068 ROM Sources
aralbrec · Wed, 16 Jun 2004 07:24
--- In [email], Jeff Burrell <jburrell7@y...> wrote:
> After examining the 2068 schematics, it would seem that a small
board that plugs onto the rear expansion could do the trick. You
would remove the EXROM from the motherbord and then plug the
expansion board with a new EXROM onto the 2068. This would allow for
use of a flash with a full 64K of available memory.
I like the idea of something hanging off the back
even better. But the EXROM doesn't have to be replaced,
just pull /BE low on power up. Then no modifications
are needed at all, always a plus.
>I would be partial to having at least one high speed (116Kb or more)
RS-232 link to allow communication with a PC. This would allow for
display and control of the diagnostics as well as upload of any dock
bank devices.
I would lean toward keeping such a device as simple
and cheap as possible and save anything fancy for
a bigger project. But adding some sort of serial
device for connection to a PC might be an idea with
some merit as long as it would also be simple.
- for diagnostics, I'm not sure how useful it
would be: it would really depend on what kind
of diagnostics would be performed. With such
a serial link I start to think of a monitor /
debugger but that would suddenly make this into
a bigger project :-)
- I like the idea of being able to save images
from the PC to a cartridge (see below) or vice
versa to make cartridge images of existing cart
software.
- If the serial link is there, it might as well
be possible to download snapshots of software
obtained from the internet directly to the
2068 RAM, and maybe vice versa.
One thing I was going to propose to you is designing
new cartridges for the 2068. The cartridge would
have 64K of nonvolatile RAM (whatever form that takes)
with the ability to program 8k chunks to behave as ROM
or RAM. The idea is to allow the user to create
any kind of cartridge he wants. Eg: save a Spectrum
ROM to the cart to create a Spectrum emulator. Or
make a copy of O/S 64 or any other Timex cart
software. Or the user could just use the cart as
extra RAM. The cart is removeable whilst retaining
its contents and is reusable, allowing its contents
to be changed at any time.
These two projects might go hand in hand.
Alvin
5. Re: [ts2068] Re: 2068 ROM Sources
Jeff Burrell · Wed, 16 Jun 2004 20:42
aralbrec <[email]> wrote:
>I like the idea of something hanging off the back
even better. But the EXROM doesn't have to be replaced,
just pull /BE low on power up. Then no modifications
are needed at all, always a plus.
True, but /BE disables all memory on the main board. I think this means that no video would be available.
I would lean toward keeping such a device as simple
and cheap as possible and save anything fancy for
a bigger project. But adding some sort of serial
device for connection to a PC might be an idea with
some merit as long as it would also be simple.
Granted about simple but if one is going to the trouble to lay out a PCB, adding a few bells and whistles doesn't add too much cost. Anyway, just don't stuff what you don't want.
- for diagnostics, I'm not sure how useful it
would be: it would really depend on what kind
of diagnostics would be performed. With such
a serial link I start to think of a monitor /
debugger but that would suddenly make this into
a bigger project :-)
- I like the idea of being able to save images
from the PC to a cartridge (see below) or vice
versa to make cartridge images of existing cart
software.
- If the serial link is there, it might as well
be possible to download snapshots of software
obtained from the internet directly to the
2068 RAM, and maybe vice versa.
A maximally usable diagnostic/debugger should have some way of reporting and being controlled. Since PCs are ubiquitous (for good or ill) they are a good candidate for a remote display and control terminal. At any rate they are sure cheaper and easier to find than a VT100. :)
One thing I was going to propose to you is designing
new cartridges for the 2068. The cartridge would
have 64K of nonvolatile RAM (whatever form that takes)
with the ability to program 8k chunks to behave as ROM
or RAM. The idea is to allow the user to create
any kind of cartridge he wants. Eg: save a Spectrum
ROM to the cart to create a Spectrum emulator. Or
make a copy of O/S 64 or any other Timex cart
software. Or the user could just use the cart as
extra RAM. The cart is removeable whilst retaining
its contents and is reusable, allowing its contents
to be changed at any time.
These two projects might go hand in hand.
Dallas and TI make battery backed SRAM modules that would be good for this application. The only problem is the formfactor. I think the modules are too tall to allow the cart door to close. My first choice would be to design a board that plugs onto the expansion connector that uses /ROSCS and acts like a cart.
I guess the question is how much demand would there would be for an expansion interface that would add memory (2MB SRAM) and some other peripherals (maybe USB 1.1 and/or IDE). This would allow diagnostics/debugging as well as add to the capabilities of the base machine.
Yahoo! Groups SponsorADVERTISEMENT
---------------------------------
Yahoo! Groups Links
To visit your group on the web, go to:
http://groups.yahoo.com/group/ts2068/
To unsubscribe from this group, send an email to:
[email]
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
---------------------------------
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
6. Re: [ts2068] Re: 2068 ROM Sources
Jeff Burrell · Thu, 17 Jun 2004 16:40
Alvin;
If the 2068TM is correct, the problem with /BE is that it disables all memory on the main board. No stack, no video, etc. The options are /ROSCS or removing the EXROM and using its select signal. /ROSCS with a cart slot on the expansion is the preferred method for pure plug-and play.
I've been wanting to do a larger project for the 2068 but would like it to be collaborative. Because of my work schedule (and a other for other non-2068 responsibilities) I just don't have the time to do both the hardware and support software for a useful device in what I consider to be a reasonable amount of time (about 1 year). I don't know if the Sinclair community is up for a harware/software project for the 2068.
I've been trolling the commodore groups to see if there would be interest for this type of project for the C64 or C128. The commodore community still seems to have a fire for keeping their classic machines usable in today's world but I don't know if the same is true for the Sinclair community. I will need to converge on a decision soon whether my project will be Commodore or Sinclair oriented.
aralbrec <[email]> wrote:
--- In [email], Jeff Burrell <jburrell7@y...> wrote:
> After examining the 2068 schematics, it would seem that a small
board that plugs onto the rear expansion could do the trick. You
would remove the EXROM from the motherbord and then plug the
expansion board with a new EXROM onto the 2068. This would allow for
use of a flash with a full 64K of available memory.
I like the idea of something hanging off the back
even better. But the EXROM doesn't have to be replaced,
just pull /BE low on power up. Then no modifications
are needed at all, always a plus.
>I would be partial to having at least one high speed (116Kb or more)
RS-232 link to allow communication with a PC. This would allow for
display and control of the diagnostics as well as upload of any dock
bank devices.
I would lean toward keeping such a device as simple
and cheap as possible and save anything fancy for
a bigger project. But adding some sort of serial
device for connection to a PC might be an idea with
some merit as long as it would also be simple.
- for diagnostics, I'm not sure how useful it
would be: it would really depend on what kind
of diagnostics would be performed. With such
a serial link I start to think of a monitor /
debugger but that would suddenly make this into
a bigger project :-)
- I like the idea of being able to save images
from the PC to a cartridge (see below) or vice
versa to make cartridge images of existing cart
software.
- If the serial link is there, it might as well
be possible to download snapshots of software
obtained from the internet directly to the
2068 RAM, and maybe vice versa.
One thing I was going to propose to you is designing
new cartridges for the 2068. The cartridge would
have 64K of nonvolatile RAM (whatever form that takes)
with the ability to program 8k chunks to behave as ROM
or RAM. The idea is to allow the user to create
any kind of cartridge he wants. Eg: save a Spectrum
ROM to the cart to create a Spectrum emulator. Or
make a copy of O/S 64 or any other Timex cart
software. Or the user could just use the cart as
extra RAM. The cart is removeable whilst retaining
its contents and is reusable, allowing its contents
to be changed at any time.
These two projects might go hand in hand.
Alvin
Yahoo! Groups SponsorADVERTISEMENT
---------------------------------
Yahoo! Groups Links
To visit your group on the web, go to:
http://groups.yahoo.com/group/ts2068/
To unsubscribe from this group, send an email to:
[email]
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
---------------------------------
Do you Yahoo!?
Read only the mail you want - Yahoo! Mail SpamGuard.
7. Re: 2068 ROM Sources
aralbrec · Tue, 29 Jun 2004 17:50
It looks like it took a while for these messages
to circulate. Someone must have been on vacation :-)
> If the 2068TM is correct, the problem with /BE is that it
disables all memory on the main board. No stack, no video, etc. The
options are /ROSCS or removing the EXROM and using its select
signal. /ROSCS with a cart slot on the expansion is the preferred
method for pure plug-and play.
Video is still generated from the 16K of RAM owned
by the SCLD (ie from the usual place). However if
/BE is active the z80 will not be able to write
into the display. This is no different from the
/ROSCS situation because if either the EXROM
or DOCK is paged in in place of the 16K area occupied
by the display, the z80 will also not be able to write
into the display, which is mapped into the HOME bank.
There is some software gymnastics involved if one
wants to write into a cartridge in the DOCK bank
whether or not /ROSCS or /BE is used, but it is
easier to use /BE. This is because you can't
have the EXROM and DOCK bank active at the same
time. The memory space is either combinations of
HOME+EXROM or HOME+DOCK 8k chunks. If the plan
is to have the hardware exist in the EXROM bank
and you would want to write into a cartridge
in the DOCK bank, you would have to first copy
the data into the HOME bank's RAM along with some
copy code, jump into the copy code in the HOME
bank, disable the EXROM and enable the DOCK bank,
copy the bytes from HOME bank to the cartridge,
disable the DOCK bank + reenable the EXROM and
return into the EXROM again.
Use of /BE allows extended memory to be present
in the memory space + HOME bank chunks + DOCK
bank chunks. It would be possible to write
directly into an attached cartridge. You'd still
have to worry about how to copy into the bottom
8k of a cartridge (if the software is located in
the bottom 8k of the /BE bank) and this would mean
either copying the copy code into the HOME bank
to do the bottom 8k or having a second copy of
the copy code in the 8k-16k area of the /BE bank.
Anyway for such a simple device, my initial
thoughts were an arrangement like:
* one 8 bit latch mapped into the i/o space,
with each bit corresponding to an 8k chunk.
If 1, the /BE bank is enabled in that chunk.
* one 8:1 mux, with the 8 bits from the latch
as input and the A15,A14,A13 address lines as
selector. The output of the mux would be 1
if the /BE memory should be visible and 0 if
internal memory should be visible.
* an NPN transistor that pulls /BE low if the
output of the mux is 1.
With this arrangement, you can have /BE memory
optionally visible in any 8k chunk of the 64k
memory space. It would be possible to have
the 16K video RAM visible so that you can write
to the display and you could have the HOME bank
paged in to use as RAM for the stack elsewhere.
There are existing devices that use /BE --
anything with an NMI snapshot button (like
the JLO disk interface) and I'm not sure what
AERCO did for its 64k RAM bank. Ideally
you would want some kind of daisy chain to
implement a priority scheme for /BE devices
so they won't conflict. No existing devices
support this, however, so they would have to be
first in the chain. I'm sure there are issues
to think about vis-a-vis compatibility and if
that's even necessary (though I suspect it is
if it were possible to load up snapshots from
the PC -- someone would probably want to snap
them to local disk).
Alvin
8. Re: 2068 ROM Sources
aralbrec · Tue, 29 Jun 2004 18:21
--- In [email], Jeff Burrell <jburrell7@y...> wrote:
> A maximally usable diagnostic/debugger should have some way of
reporting and being controlled. Since PCs are ubiquitous (for good
or ill) they are a good candidate for a remote display and control
terminal. At any rate they are sure cheaper and easier to find than
a VT100. :)
:-) I'm open to it and would need to see some kind
of list of supported features. I am just afraid that
if this is too ambitious, it could turn into a lot of
work.
> Dallas and TI make battery backed SRAM modules that would be good
for this application. The only problem is the formfactor. I think
the modules are too tall to allow the cart door to close.
It's been a long while since I've shopped around
for parts and at that time NVRAMs were way too
expensive. However, I did take a look around
in the past week and found 32Kx8 NVRAMS at about
US$10 and 128Kx8 NVRAMs at about US$16 in single
quantities by mail order before shipping and taxes.
These are the ideal parts and I think the price
is right. About fitting into the cart slot --
I think they will. I haven't actually measured
the available space, but I believe there is
space under the door but beyond the plastic lip-
hood of the cart slot.
I would be inclined to allow the cart to
accommodate a single NVRAM chip of 128Kx8
size and higher. 64K of it would be the
dock bank; the rest could be treated as a
RAMdisk storing compressed data. At power
up, the cart would select the previously
saved configuration of the 64K DOCK bank,
and (maybe) if certain keys are pressed,
a menu of what is in the RAMdisk could come
up, allowing a different configuration to
be selected.
The hardware would actually allow full
access to the entire NVRAM in a limited
way but I am thinking the primary goal
of the cart would be as a small portable
storage device and I have no interest in
having it compete against any larger RAM
expansion project. I only added the
RAMdisk bit because a 64Kx8 NVRAM does
not exist and it is cheaper to buy a
128Kx8 NVRAM than two 32Kx8 NVRAMs.
Alvin
9. Re: 2068 ROM Sources
aralbrec · Tue, 29 Jun 2004 19:15
--- In [email], Jeff Burrell <jburrell7@y...> wrote:
> I've been wanting to do a larger project for the 2068 but would
like it to be collaborative. Because of my work schedule (and a
other for other non-2068 responsibilities) I just don't have the time
to do both the hardware and support software for a useful device in
what I consider to be a reasonable amount of time (about 1 year). I
don't know if the Sinclair community is up for a harware/software
project for the 2068.
I still have interest in a larger project, which
is why I have been trying to beat down the specs
for this addon. My only intent was to make it
possible to preserve cartridge software in the
near future, which is not easily possible now.
I would be interested in a collaboration to finish
up a larger project, but I have been concentrating
on the software side of things lately and have been
trying to limit the number of things I am doing in
order to actually finish the software projects
I have going in the limited hobby time that I (and
everyone) must live with. These days hobby time
runs from about 12am to 1am :-) In other words I
am not quite ready to contribute in a significant
way. However, if you are ready to go ahead and
start the hw (or maybe you've done a lot already?),
I wouldn't mind hashing out the features and how
things work and I'll commit to contributing in a
bigger way down the road.
About the demand that might exist, I don't know.
I can think of 5 people who would probably build
/ buy one (including me and you). There are
88 people on this list but it is a rather quiet
list. I'm not sure if such a project would
stir up people enough to dust off their 2068s
and see what it could be.
A lot of the hardware could be adapted for
the Spectrum to appeal to the larger Sinclair
community. However, the Spectrums (not
including the +3) have much more limited
banking ability so things might have to be
scaled back for them, especially on the
software side.
Alvin
10. Re: [ts2068] Re: 2068 ROM Sources
Jack Boatwright · Thu, 1 Jul 2004 14:38:
Count me in as one of the five mentioned below. Although I am not
a 'technowiz', I'd certainly avail myself to help in any way I
possibly can.
Jack
> From: "aralbrec" <[email]>
>
> --- In [email], Jeff Burrell <jburrell7@y...>
wrote:
>
> > I've been wanting to do a larger project for the 2068 but
would
> like it to be collaborative. Because of my work schedule (and a
> other for other non-2068 responsibilities) I just don't have the
time
> to do both the hardware and support software for a useful device
in
> what I consider to be a reasonable amount of time (about 1
year). I
> don't know if the Sinclair community is up for a
harware/software
> project for the 2068.
>
> I still have interest in a larger project, which
> is why I have been trying to beat down the specs
> for this addon. My only intent was to make it
> possible to preserve cartridge software in the
> near future, which is not easily possible now.
>
> I would be interested in a collaboration to finish
> up a larger project, but I have been concentrating
> on the software side of things lately and have been
> trying to limit the number of things I am doing in
> order to actually finish the software projects
> I have going in the limited hobby time that I (and
> everyone) must live with. These days hobby time
> runs from about 12am to 1am :-) In other words I
> am not quite ready to contribute in a significant
> way. However, if you are ready to go ahead and
> start the hw (or maybe you've done a lot already?),
> I wouldn't mind hashing out the features and how
> things work and I'll commit to contributing in a
> bigger way down the road.
>
> About the demand that might exist, I don't know.
> I can think of 5 people who would probably build
> / buy one (including me and you). There are
> 88 people on this list but it is a rather quiet
> list. I'm not sure if such a project would
> stir up people enough to dust off their 2068s
> and see what it could be.
>
> A lot of the hardware could be adapted for
> the Spectrum to appeal to the larger Sinclair
> community. However, the Spectrums (not
> including the +3) have much more limited
> banking ability so things might have to be
> scaled back for them, especially on the
> software side.
>
> Alvin
11. Large project
Jarek Adamski · Thu, 08 Jul 2004 09:42
--- In [email], Jeff Burrell <jburrell7@y...> wrote:
> I don't know if the Sinclair community is up for a
> harware/software project for the 2068.
I see no big use for TS2068 specific project.
The project should include also other ZX Spectrum
compatibile computers (at least include TC2048).
(This can be also extra circutit that turns ordinary
ZX Spectrum into a TS2068 - an external Z80 will do
much of work unless high screen resolution is needed.)
Except "Sinclair community" people I found another
target group - computer collectors. Most of them
(from my experience) would like to have an interface
that helps test the hardware and load software in a
fast and solid way.
But extra work must be done to find them, as they
usually doesn't search for new projects.
Also, there are people, who would like upgrade and
use their old computers, but they still don't know
if it is possible. They doesn't search such
possibilities being busy by work, girl and TV.
There are many ambitious projects over the Internet.
Most people I know (including me) would like to have
them at home (or just see and amuse). But there are
too many things to do and people are lazy - so the
project should be ready-for-use and delivered to
their hands direcly.
Recently I've got a note about new (upgraded) main
board for Didaktik (a ZX clone). My thinking was
"Yes, I would like to have new main board for my
ZX Spectrum, even at $60USD. But I don't own original
Didaktik (so I cannot upgrade). So this has no use
for me. EOT." Then I only copied the documentation
to my page and reviewed it (because I'm interested
in technical details and can read them, unlike most
of people that will finish at this point).
My opinion is, new projects make sens when many
people (say, at least 50) will use them. The new
projects must be as wide and flexible as possible
and offered in a commercial way (i.e. supported
by a marketing and sell system). (However, they
don't have a commercial sense, as are made for
fun, not for money.)
Jarek Adamski
12. Re: 2068 ROM Sources
Jarek Adamski · Thu, 08 Jul 2004 10:00
--- In [email], "aralbrec" <aralbrec@i...> wrote:
> and I'm not sure what AERCO did for its 64k RAM bank.
DOCK only (the ROM replaces first 8kB as LROS, then is
switched off).
Jarek Adamski
13. Re: [ts2068] Re: 2068 ROM Sources
Don Dindang · Thu, 8 Jul 2004 21:57:
Please count me as one of the five too.
Thanks,
Watchara
--- Jack Boatwright <[email]> wrote:
> Count me in as one of the five mentioned below.
> Although I am not
> a 'technowiz', I'd certainly avail myself to help in
> any way I
> possibly can.
>
> Jack
>
>
> > From: "aralbrec" <[email]>
> >
> > --- In [email], Jeff Burrell
> <jburrell7@y...>
> wrote:
> >
> > > I've been wanting to do a larger project for
> the 2068 but
> would
> > like it to be collaborative. Because of my work
> schedule (and a
> > other for other non-2068 responsibilities) I just
> don't have the
> time
> > to do both the hardware and support software for a
> useful device
> in
> > what I consider to be a reasonable amount of time
> (about 1
> year). I
> > don't know if the Sinclair community is up for a
> harware/software
> > project for the 2068.
> >
> > I still have interest in a larger project, which
> > is why I have been trying to beat down the specs
> > for this addon. My only intent was to make it
> > possible to preserve cartridge software in the
> > near future, which is not easily possible now.
> >
> > I would be interested in a collaboration to finish
> > up a larger project, but I have been concentrating
> > on the software side of things lately and have
> been
> > trying to limit the number of things I am doing in
> > order to actually finish the software projects
> > I have going in the limited hobby time that I (and
> > everyone) must live with. These days hobby time
> > runs from about 12am to 1am :-) In other words I
> > am not quite ready to contribute in a significant
> > way. However, if you are ready to go ahead and
> > start the hw (or maybe you've done a lot
> already?),
> > I wouldn't mind hashing out the features and how
> > things work and I'll commit to contributing in a
> > bigger way down the road.
> >
> > About the demand that might exist, I don't know.
> > I can think of 5 people who would probably build
> > / buy one (including me and you). There are
> > 88 people on this list but it is a rather quiet
> > list. I'm not sure if such a project would
> > stir up people enough to dust off their 2068s
> > and see what it could be.
> >
> > A lot of the hardware could be adapted for
> > the Spectrum to appeal to the larger Sinclair
> > community. However, the Spectrums (not
> > including the +3) have much more limited
> > banking ability so things might have to be
> > scaled back for them, especially on the
> > software side.
> >
> > Alvin
>
>
>
>
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail
14. Re: [ts2068] Re: 2068 ROM Sources
Bill aka OhnO the Clown · Fri, 9 Jul 2004 08:35:
I believe that the intrest in this project, or at
least in the fruits thereof, has long past the "Five"
mentioned.
I am also interested though I am not a "techno- wiz"
either. Thus I would not be of much help in the
hardware side of things. Yet as a probable buyer and
later with some user programming count me in.
Thanks,
__________________________________
Do you Yahoo!?
Read only the mail you want - Yahoo! Mail SpamGuard.
http://promotions.yahoo.com/new_mail
15. Re: 2068 ROM Sources
rafael_mnrq · Tue, 03 Aug 2004 03:28
I need help.
I received files "TS2068 ROM dis-assembly" on March/04
My computer crashed, I lost those files.
I need a new copy.
rafael
16. Re: 2068 ROM Sources
Jeff · Tue, 03 Aug 2004 20:21
Rafael;
Those files are now in the files area here.
--- In [email], "rafael_mnrq" <rafael_mnrq@y...> wrote:
> I need help.
>
> I received files "TS2068 ROM dis-assembly" on March/04
> My computer crashed, I lost those files.
>
> I need a new copy.
>
> rafael
Indexed under
TS2068 / TC2068 · Cartridges, EPROM & dumping · Hardware projects & new boards