headers
Darren A | 2 Dec 2008 07:01
Picon

Re: announcement to reserve "CoCoNet" title

On 11/29/08, Roger Taylor  wrote:
> As the subject says, I'm reserving the name CoCoNet for a new product
> unless some other title exists in the CoCo world.
>
> --
> Roger Taylor

A product with the name "CoCo Net" has been announced, but I believe
Chuck has abandoned it:

<http://www.retroengineering.com/net.shtml>

Darren

--
Coco mailing list
Coco@...
http://five.pairlist.net/mailman/listinfo/coco
Permalink | Reply | 0 comments |
headers
Guillaume Major | 5 Dec 2008 03:00
Picon

2 new AGI games

Hi coco fans,

I have adapted two more fan made AGI games for the coco: Time Quest and V 
Demo. Although they have the status of "demo", these games are very well 
done and contains good puzzles.

You can download them at http://goyim.dyndns.org:8080/coco/Sierra.Games/

Enjoy!

Guillaume

--
Coco mailing list
Coco@...
http://five.pairlist.net/mailman/listinfo/coco
Permalink | Reply | 4 comments |
headers
N8WQ | 5 Dec 2008 05:36
Picon

Re: 2 new AGI games

Guillaume,
It is nice of you to put up the games for download.
Thanks...

Alan

Guillaume Major wrote:
> Hi coco fans,
>
> I have adapted two more fan made AGI games for the coco: Time Quest and V 
> Demo. Although they have the status of "demo", these games are very well 
> done and contains good puzzles.
>
> You can download them at http://goyim.dyndns.org:8080/coco/Sierra.Games/
>
> Enjoy!
>
> Guillaume
>
>
>
>
>
> --
> Coco mailing list
> Coco@...
> http://five.pairlist.net/mailman/listinfo/coco
>
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Roger Taylor | 7 Dec 2008 04:07
Gravatar

CoCoNet status

As of 12/6/08, the CoCoNet project is moving forward quickly:

CoCoNet is a base system patched into Disk BASIC 1.1 that allows you 
to mount virtual disks from your PC or the web (through the PC's 
connection), and also copy files from the PC or the web and put them 
on currently-mounted virtual disks.  There's no need to move back and 
forth between the CoCo and PC.  The PC server software gives what the 
CoCo asks for.

some possible Disk BASIC 1.1 commands:

DRIVE 0,"c:\any.dsk"
DRIVE 0,"http://www.coco3.com/coconet/dsk/d01.dsk" (read-only)
DRIVE 0,"d02"  (automatically points to coco3.com coconet virtual 
disk folder) + ".dsk"
DRIVE 0,"os9"  (mounts os9.dsk stored on coco3.com/coconet server)
DRIVE 0,"http://www.yourserver.com/nitros9.os9"
--ability to turn virtual disks on/off

(quickly grab internet files or PC files and port them instantly onto 
your mounted virtual disks)
WLOAD "http://www.coco3.com/somegame.bin","game.bin"  (automatic LOADM format)
WLOAD "http://www.anyserver.com/calc.bas","calc.bas" (automatic ASCII 
or binary format detected)
WLOAD "http://www.stocks.com/latest.dat","stocks.dat"

Get the idea?  Is all of this fast??  YES.  57600 bps on a CoCo 1 or 
2, and 115200 bps on a CoCo 3 through the bitbanger port.  USB serial 
dongles work great, with any COM#, not just 1 through 4.  I use COM8 
in my tests.
(Continue reading)

Permalink | Reply | 22 comments |
headers
Darren A | 7 Dec 2008 05:29
Picon

Re: CoCoNet status

On 12/6/08, Roger Taylor wrote:
>
> <snip>
>
> Get the idea?  Is all of this fast??  YES.  57600 bps on a CoCo 1 or
> 2, and 115200 bps on a CoCo 3 through the bitbanger port.  USB serial
> dongles work great, with any COM#, not just 1 through 4.  I use COM8
> in my tests.

Roger,

Have you tested this with a CoCo 1?  Recent tests I've done have led
me to the conclusion that the CoCo 1 hardware is not capable of
transmitting 57600 bps through the bit banger port, although it can
receive data at that speed. My guess is that the opamp used for the
level translation to +/- 12 volts can't operate that fast.  You will
probably have to lower the transmission speed or specify a CoCo 2 as
the minimum requirement.

Darren

--
Coco mailing list
Coco@...
http://five.pairlist.net/mailman/listinfo/coco
Permalink | Reply | 2 comments |
headers
Roger Taylor | 7 Dec 2008 06:45
Gravatar

Re: CoCoNet status

At 10:29 PM 12/6/2008, you wrote:
>Roger,
>
>Have you tested this with a CoCo 1?  Recent tests I've done have led
>me to the conclusion that the CoCo 1 hardware is not capable of
>transmitting 57600 bps through the bit banger port, although it can
>receive data at that speed. My guess is that the opamp used for the
>level translation to +/- 12 volts can't operate that fast.  You will
>probably have to lower the transmission speed or specify a CoCo 2 as
>the minimum requirement.
>
>Darren

Noted.  I have two CoCo 1's I will test on tonight.

Btw, CoCoNet was just ROM'ed 5 minutes ago.  The CoCo powers up 
CoCoNet READY!  The ROM is in an EPROM Pak and no real floppy 
controller is connected.  Problem is, it's a 27128 16K EPROM, so I'm 
not sure if this would work in a CoCo 3.

This involved first CLOADM'ing a single-record version of the DOS 
patch which goes into all-RAM mode, patches DOS, executes some init 
routines, then I build the DOS overlay version from the Rainbow IDE, 
mount that virtual disk from the CoCo 2, copy the overlay.rom from 
the virtual disk onto the MPROM floppy disk, etc. etc. it took a 
while to figure out how I was going to do this.  Now that Disk BASIC 
is CoCoNet patched, hopefully the development process will speed up 
greatly more.

I realize that in order to produce CoCoNet that it would compete with
(Continue reading)

Permalink | Reply | 4 comments |
headers
Roger Taylor | 7 Dec 2008 07:40
Gravatar

Re: CoCoNet status

At 10:29 PM 12/6/2008, you wrote:

>Have you tested this with a CoCo 1?  Recent tests I've done have led
>me to the conclusion that the CoCo 1 hardware is not capable of
>transmitting 57600 bps through the bit banger port, although it can
>receive data at that speed. My guess is that the opamp used for the
>level translation to +/- 12 volts can't operate that fast.  You will
>probably have to lower the transmission speed or specify a CoCo 2 as
>the minimum requirement.
>
>Darren

115200 bps was just confirmed on the CoCo *2*.  I couldn't do this 
with the tape version of CoCoNet because it runs in all-RAM mode on 
the 2, which doesn't allow the 2mhz POKE to work.  Now in ROM, it works.

I surely hope the CoCo 1's don't have an issue like you said.  Giving 
an old gray CoCo internet access is what I aim for.  I'm not sure if 
I have enough space to put 38400 bps routines in, but if needed I'll 
optimize the best I can and try to squeeze it in.

--

-- 
Roger Taylor

http://www.wordofthedayonline.com

--
Coco mailing list
Coco@...
http://five.pairlist.net/mailman/listinfo/coco
(Continue reading)

Permalink | Reply | 0 comments |
headers
Art Flexser | 7 Dec 2008 12:55
Favicon

Re: CoCoNet status

On Sat, 6 Dec 2008, Roger Taylor wrote:

> 
> Btw, CoCoNet was just ROM'ed 5 minutes ago.  The CoCo powers up 
> CoCoNet READY!  The ROM is in an EPROM Pak and no real floppy 
> controller is connected.  Problem is, it's a 27128 16K EPROM, so I'm 
> not sure if this would work in a CoCo 3.
> 

If you need to have Super Extended Basic available on the CoCo 3, you can use
the same approach I used for Extended ADOS-3, which resides in a 27128.  When
you need to call a ROM routine that is in the upper 8K of your EPROM, you switch
to ROM mode first, and switch back to ROM/RAM mode on the return from the
routine (to somewhere not in the upper 8K) to re-enable Super Ext. Basic.  
(Have your ROM test whether it is running on a CoCo 3 during initialization, and
do this only if a CoCo 3 is being used.)

Art

--
Coco mailing list
Coco@...
http://five.pairlist.net/mailman/listinfo/coco
Permalink | Reply | 3 comments |
headers
George Ramsower | 7 Dec 2008 16:59
Picon

Re: CoCoNet status

----- Original Message ----- 
From: "Roger Taylor"

> As of 12/6/08, the CoCoNet project is moving forward quickly:
>
> CoCoNet is a base system patched into Disk BASIC 1.1 that allows you to 
> mount virtual disks from your PC or the web (through the PC's connection), 
> and also copy files from the PC or the web and put them on 
> currently-mounted virtual disks.  There's no need to move back and forth 
> between the CoCo and PC.  The PC server software gives what the CoCo asks 
> for.
>

 I'm wondering if something like this could be made to handle OS-9 and use a 
PC to be the drive for the OS.

 This would be very nice to eliminate the need for a floppy or hard drive. 
Of course, I understand that OS-9 would  need a driver to deal with this.

 It wouldn't bother me a bit to make a coco a slave to a PC if the PC could 
act as a mass storage device with OS-9 as the OS for the coco.

 Of course, a new ROM would be in order to make the boot happen.

  Since my PC is almost always on, this could work for me.

 It would seem that even a CC One (64K) could benefit from this even if it 
did work a little slower. No disk drives at all !

George, dreaming.
(Continue reading)

Permalink | Reply | 17 comments |
headers
Roger Taylor | 7 Dec 2008 18:55
Gravatar

Re: CoCoNet status

At 05:55 AM 12/7/2008, you wrote:
>On Sat, 6 Dec 2008, Roger Taylor wrote:
>
> >
> > Btw, CoCoNet was just ROM'ed 5 minutes ago.  The CoCo powers up
> > CoCoNet READY!  The ROM is in an EPROM Pak and no real floppy
> > controller is connected.  Problem is, it's a 27128 16K EPROM, so I'm
> > not sure if this would work in a CoCo 3.
> >
>
>If you need to have Super Extended Basic available on the CoCo 3, you can use
>the same approach I used for Extended ADOS-3, which resides in a 27128.  When
>you need to call a ROM routine that is in the upper 8K of your 
>EPROM, you switch
>to ROM mode first, and switch back to ROM/RAM mode on the return from the
>routine (to somewhere not in the upper 8K) to re-enable Super Ext. Basic.
>(Have your ROM test whether it is running on a CoCo 3 during 
>initialization, and
>do this only if a CoCo 3 is being used.)
>
>Art

It seems like this should work on any CoCo using the same code.  Is 
there a reason why I should check whether it's a CoCo 3 or not?  I 
can understand if I'm having to use the GIME to do internal/external 
ROM switching and so forth to access the upper 16K of my ROM then 
CoCo 1,2 <> 3 checking might be necessary.

--

-- 
Roger Taylor
(Continue reading)

Permalink | Reply | 2 comments |

Gmane