[Coco] CoCoNet 1.18 test

[Jorge Renato Machin Ibarra]

Roger:

 

I found the error. I had my Deluxe Wireless RS-232 Pak configured to 9600 bauds. Thank you for guide me!

 

CoCoNet takes about 1 to 15 seconds  to connect to  my PC. I think it is very fast and gives a quick way to checkout programs in .dsk files.

 

Version 1.19 has a little bug. At boot time It shows drive 0 as CNET-6551 but CNET-6551 is actually drive 2 in my system and shows the I/O error at startup.

 

Do you have more Deluxe Wireless RS-232 Paks? I like CoCoNet very much but I'll miss the terminal program (I don't want to interchange eproms). A cartridge with Bluetooth and SD card reader funtionality would be great!

 

Thanks

 

Jorge Machin

 

 
> Date: Sat, 8 May 2010 18:39:01 -0500
> To: coco at maltedmedia.com
> From: operator at coco3.com
> Subject: Re: [Coco] CoCoNet 1.18 test
> 
> At 03:50 PM 5/8/2010, you wrote:
> 
> >Roger:
> >Today I tested CoCoNet, but I think I'm missing something because it 
> >did not work. What I did is this:
> >1. I started the server with my bluetooth configured to use com3 and 
> >"allow other devices to see my device" option selected in my windows vista box.
> >2. I booted my coco 2 with my Deluxe Wireless RS-232 Pak and got this:
> >COCONET 1.18
> >CNET-SIO: NO
> >CNET-6551 : NO
> >MICROSD PAK: NO
> 
> 
> Jorge, here's the CoCoNet 1.19 ROM which does away with the ?IO Error 
> if no disk is present in your real FDC. The BluetoothReady routine 
> looks good so I'm waiting on your response on that. The initial 
> setup of letting the PC accept calls from the CoCo over the air can 
> be tricky or just plum silly easy depending on what bluetooth stack 
> your PC uses (Windows, Broadcom, etc.). Some of them have better 
> dialogs and more checkboxes.
> 
> On the PC, remove the CoCo or EB301 connection and do it over again 
> and make note of the *incoming* COM port it assigns and then use that 
> in your CoCoNet server .ini file or at the server prompts.
> 
> The server will open the Incoming COM port and wait on the connection 
> to happen. If you turn the CoCo off, I found it's best to wait about 
> 15 seconds before powering back up if you want to the server to 
> settle and respond as expected. That is, the underlying bluetooth 
> stack has to deal with the loss of connection and reset itself and 
> then the server gets the news, etc. It's all smooth and easy once 
> the PC is accepting incoming connections.
> 
 		 	   		  
_________________________________________________________________
Hotmail: Trusted email with Microsoft’s powerful SPAM protection.
https://signup.live.com/signup.aspx?id=60969