dwhyte Posted April 22, 2007 Share Posted April 22, 2007 (edited) Does anyone know what these are? Unexpected command frame at state 3. Unexpected command frame at state 3. Unexpected command frame at state 3. Unexpected command frame at state 60. Unexpected command frame at state 3. atari800 spit these statements out into the console. Are these ANTIC debug statements? Edited April 23, 2007 by dwhyte Quote Link to comment Share on other sites More sharing options...
Urchlay Posted April 22, 2007 Share Posted April 22, 2007 atari800 spit these statements out into the console. Are these ANTIC debug statements? Atari800, the Atari 8-bit emulator? Never seen such a thing, they sound more like something I'd expect to see from AtariSIO or Atari810 (drive emulation software for the SIO2PC). In any case, they're SIO debug messages (related to some peripheral, a disk drive/printer/etc)... no idea why you're seeing them though. "state 3" and "state 60" don't mean anything outside of whatever program that is, would have to see its documentation or source to know what they mean. Quote Link to comment Share on other sites More sharing options...
dwhyte Posted April 22, 2007 Author Share Posted April 22, 2007 (edited) atari800 spit these statements out into the console. Are these ANTIC debug statements? Atari800, the Atari 8-bit emulator? Never seen such a thing, they sound more like something I'd expect to see from AtariSIO or Atari810 (drive emulation software for the SIO2PC). In any case, they're SIO debug messages (related to some peripheral, a disk drive/printer/etc)... no idea why you're seeing them though. "state 3" and "state 60" don't mean anything outside of whatever program that is, would have to see its documentation or source to know what they mean. I'm modifying MyPicoDOS to look the way I want (spent the last half an hour finally figuring out that disk access with interrupts on is bad...kudos to the lucasfilm intro programmers)... Never expected SIO debugs. There's no disk access going on when they get spit out... Using linux, debug is going to the terminal. Edited April 22, 2007 by dwhyte Quote Link to comment Share on other sites More sharing options...
Urchlay Posted April 22, 2007 Share Posted April 22, 2007 I'm modifying MyPicoDOS to look the way I want (spent the last half an hour finally figuring out that disk access with interrupts on is bad...kudos to the lucasfilm intro programmers)... Never expected SIO debugs. There's no disk access going on when they get spit out... Using linux, debug is going to the terminal. Maybe you should turn off the "fast SIO" OS patch speedup in Atari800. Worth a try anyway. Quote Link to comment Share on other sites More sharing options...
dwhyte Posted April 22, 2007 Author Share Posted April 22, 2007 (edited) I'm modifying MyPicoDOS to look the way I want (spent the last half an hour finally figuring out that disk access with interrupts on is bad...kudos to the lucasfilm intro programmers)... Never expected SIO debugs. There's no disk access going on when they get spit out... Using linux, debug is going to the terminal. Maybe you should turn off the "fast SIO" OS patch speedup in Atari800. Worth a try anyway. It was turned off... Doesn't seem to happen with the SIO patch on... Hmm... Well here's what was churning out those debug msgs... XE_Anthol1.zip Edited April 22, 2007 by dwhyte Quote Link to comment Share on other sites More sharing options...
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.