Retro/pcjs
Watch
1
0
Fork
You've already forked pcjs
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
pcjs/versions/pcx86/1.24.0
History
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Jeff Parsons 983651610c Worked around initConnection() failures due to machines that initialize more slowly, by also allowing each machine to invoke the other's initConnection(); if it turns out to be unnecessary, it's simply ignored
2016-08-19 12:35:18 -07:00
..
common.css A (PC8080) VT100 can now connect to a (PCx86) IBM PC AT; only problem seems to be flow control now. 2016-08-18 16:46:34 -07:00
common.xsl A (PC8080) VT100 can now connect to a (PCx86) IBM PC AT; only problem seems to be flow control now. 2016-08-18 16:46:34 -07:00
components.css A (PC8080) VT100 can now connect to a (PCx86) IBM PC AT; only problem seems to be flow control now. 2016-08-18 16:46:34 -07:00
components.xsl A (PC8080) VT100 can now connect to a (PCx86) IBM PC AT; only problem seems to be flow control now. 2016-08-18 16:46:34 -07:00
document.css A (PC8080) VT100 can now connect to a (PCx86) IBM PC AT; only problem seems to be flow control now. 2016-08-18 16:46:34 -07:00
document.xsl A (PC8080) VT100 can now connect to a (PCx86) IBM PC AT; only problem seems to be flow control now. 2016-08-18 16:46:34 -07:00
machine.xsl A (PC8080) VT100 can now connect to a (PCx86) IBM PC AT; only problem seems to be flow control now. 2016-08-18 16:46:34 -07:00
manifest.xsl A (PC8080) VT100 can now connect to a (PCx86) IBM PC AT; only problem seems to be flow control now. 2016-08-18 16:46:34 -07:00
outline.xsl A (PC8080) VT100 can now connect to a (PCx86) IBM PC AT; only problem seems to be flow control now. 2016-08-18 16:46:34 -07:00
pcx86-dbg.js Worked around initConnection() failures due to machines that initialize more slowly, by also allowing each machine to invoke the other's initConnection(); if it turns out to be unnecessary, it's simply ignored 2016-08-19 12:35:18 -07:00
pcx86.js Worked around initConnection() failures due to machines that initialize more slowly, by also allowing each machine to invoke the other's initConnection(); if it turns out to be unnecessary, it's simply ignored 2016-08-19 12:35:18 -07:00