Do you mean you turned CTS/RTS handshaking off at the PC end?
I don't think you can turn it off at the BBC end and use the OS to send stuff can you? What's the osbyte call for that?
Well the only call I could find is 138 and I think that is handshake only (unless there is some other call that changes that behavour)
So I'd imagine that the Beeb is waiting for CTS to be asserted from the PC so the beeb never sends anything. Write directly to the ACIA register and see if things come out then (?&FE09=n from BASIC). If you want to write directly you /ought/ to check the status to see if the output buffer is clear to accept data, but as a test it works.
Thanks for the tip - I'll try that - The data sent from the BBC to the PC will only be at typing rates by the way.
Out of interest why do you wish to turn off handshaking?
Well what I'm actually trying to do is get the BBC to communicate with a serial to wifi device (not a PC) so I can connect the BBC to the internet.
See this thread: http://www.stardot.org.uk/forums/viewto ... =3&t=12426
To that end I've got the PC succesfully communicating with the device, althought the device is only reliable with handshaking turned off when talking to the PC so that's why I need handshaking off when connecting it to the BBC instead of the PC.
The proceedure is send AT+ 'GET' command to the device then receive the web page back from device.
That works fine with the device connected to the PC without handshaking. With handshaking it freezes up for some unknown reason.
When connected to the BBC the device never gets the AT+ command as the BBC never sends it.....(due to the original issue).
I get 3.8kB/s with an ASM reciever loop on the beeb).
I found the same thing with other serial tests in that the BBC's basic is too slow to receive all the characters but a machine code loop worked fine (at 9600 and 19200 baud)