One hassle for diagnosing tape read problems with a microbee is that it is time critically bit bashed and its standard ROM TAPE read routines don't provide a real time bit received display capability.
The microbee's predecessor - DGZ80 has a wonderful inbuilt tape bit detector. Rather than the alternating '*' between each successfully received block, the DGOS tape routines used an animated chunky graphics character to show tape data activity through out the block read. The DGZ80 could do this because it's cassette interface was partially hardware driven, software bit bashed, had no video deglitching circuit and had a bit of spare time to do so (@300 baud).
The method used to calibrate the DGZ80's cassette interface (USCI and SECI) was use the DGOS monitor to:
1. Fill the screen up with 'U's (i.e. binary code 01010101)
>F F000 F3FF 55
2. Write a test tape using
>W "TEST" T F000 F3FF
3. and then read it back using
>R
The screen would read the header and in real time you could see the screen fill up with 'U's if everything was working. If it wasn't junk characters or flashing a 'C' for CRC errors would appear.
Is that Nokia, Microsoft or both?
Pissy? Someone was forced to transition from Bigpond Cable to the NBN back in September and lost their phone number in the process. Telstra didn't port the phone number as requested. It's some 3 months later and Telstra still hasn't completed the job to get it back even with an official TIO Complaint (Telecommunications Industry Ombudsman). The latest communique with the TIO stipulated that they've been inundated with issues and have a 5 week lag time. Someone knows of a poor restaurant that's had a similar issue with their customers thinking that they've closed down because they can't be contacted. How horrible for the restaurant owners and staff!!
The microbee's predecessor - DGZ80 has a wonderful inbuilt tape bit detector. Rather than the alternating '*' between each successfully received block, the DGOS tape routines used an animated chunky graphics character to show tape data activity through out the block read. The DGZ80 could do this because it's cassette interface was partially hardware driven, software bit bashed, had no video deglitching circuit and had a bit of spare time to do so (@300 baud).
The method used to calibrate the DGZ80's cassette interface (USCI and SECI) was use the DGOS monitor to:
1. Fill the screen up with 'U's (i.e. binary code 01010101)
>F F000 F3FF 55
2. Write a test tape using
>W "TEST" T F000 F3FF
3. and then read it back using
>R
The screen would read the header and in real time you could see the screen fill up with 'U's if everything was working. If it wasn't junk characters or flashing a 'C' for CRC errors would appear.
(12-01-2021, 05:38 PM)g67wjjk Wrote:(12-01-2021, 08:03 AM)someone Wrote: Do you ever sleep?
23 years with Nokia ... 20 years, and counting, on emergency call-up in various countries. Used to working weird hours ... people get pissy/whine to Whirlpool when they can't use their phone
Is that Nokia, Microsoft or both?
Pissy? Someone was forced to transition from Bigpond Cable to the NBN back in September and lost their phone number in the process. Telstra didn't port the phone number as requested. It's some 3 months later and Telstra still hasn't completed the job to get it back even with an official TIO Complaint (Telecommunications Industry Ombudsman). The latest communique with the TIO stipulated that they've been inundated with issues and have a 5 week lag time. Someone knows of a poor restaurant that's had a similar issue with their customers thinking that they've closed down because they can't be contacted. How horrible for the restaurant owners and staff!!