DOS ain't dead

Waiting for 3 (or 3.3) microseconds? 286 and up. (Developers)

posted by RayeR , CZ, 10.12.2012, 03:09

Sorry I don't know SB programming but if there is available some status register that changes a value when device is ready it's the best way to read this status in a loop (you may add some n-cycles timeout to not hang the PC if there's is some error). Otherwise I would rather wait 1ms (it's only at once on system startup so nobody would notice such short delay) than use fixed loop counter that is dependent on CPU speed - it's a bad code. I think it's acceptable to use some counter based on number of IO reads because ISA (LPC) bus has comparable speed on 286 and modern PC. But CPU cycle was shortened by many magnitudes...

---
DOS gives me freedom to unlimited HW access.

Complete thread:

• Waiting for 3 (or 3.3) microseconds? 286 and up. - myrkraverk, 09.12.2012, 23:41 (Developers)
  • Waiting for 3 (or 3.3) microseconds? 286 and up. - RayeR, 10.12.2012, 03:09
  • Waiting for 3 (or 3.3) microseconds? 286 and up. - Japheth, 10.12.2012, 11:42
    • Waiting for 3 (or 3.3) microseconds? 286 and up. - RayeR, 10.12.2012, 18:04
  • Waiting for 3 (or 3.3) microseconds? 286 and up. - bretjohn, 10.12.2012, 15:52
    • Waiting for 3 (or 3.3) microseconds? 286 and up. - myrkraverk, 10.12.2012, 21:22
  • Waiting for 3 (or 3.3) microseconds? 286 and up. - myrkraverk, 10.12.2012, 21:16
  • Waiting for 3 (or 3.3) microseconds? 286 and up. - Rugxulo, 10.12.2012, 22:03
    • Waiting for 3 (or 3.3) microseconds? 286 and up. - myrkraverk, 13.12.2012, 14:07
      • Waiting for 3 (or 3.3) microseconds? 286 and up. - marcov, 13.12.2012, 22:51
        • Waiting for 3 (or 3.3) microseconds? 286 and up. - RayeR, 14.12.2012, 01:12