Retro/pcjs
Watch
1
0
Fork
You've already forked pcjs
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
pcjs/disks/pcx86/windows
History
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Jeff Parsons 6d019e7d9d Fixed autoMount overrides (formerly, machines that wanted to override the diskette autoMount settings for a machine would set "autoMount: ''", but that was a sledgehammer solution, especially when the goal was merely to prevent a diskette from being loaded in drive A; the preferred solution now is to set "autoMount: A: None", allowing the rest of the machine's autoMount settings, if any, to remain intact)
2017-06-17 21:30:03 -07:00
..
1.00 Bumped next release version to 1.35.0 2017-06-01 15:35:25 -07:00
1.01 Bumped next release version to 1.35.0 2017-06-01 15:35:25 -07:00
1.02 Bumped next release version to 1.35.0 2017-06-01 15:35:25 -07:00
1.03 Bumped next release version to 1.35.0 2017-06-01 15:35:25 -07:00
1.03a Bumped next release version to 1.35.0 2017-06-01 15:35:25 -07:00
1.03b Bumped next release version to 1.35.0 2017-06-01 15:35:25 -07:00
1.04 Bumped next release version to 1.35.0 2017-06-01 15:35:25 -07:00
2.0x Fixed autoMount overrides (formerly, machines that wanted to override the diskette autoMount settings for a machine would set "autoMount: ''", but that was a sledgehammer solution, especially when the goal was merely to prevent a diskette from being loaded in drive A; the preferred solution now is to set "autoMount: A: None", allowing the rest of the machine's autoMount settings, if any, to remain intact) 2017-06-17 21:30:03 -07:00
2.03 Disk manifest updates 2017-06-02 09:22:27 -07:00
2.10 Disk manifest updates 2017-06-02 09:22:27 -07:00
2.11 Disk manifest updates 2017-06-02 09:22:27 -07:00
3.00 Fixed autoMount overrides (formerly, machines that wanted to override the diskette autoMount settings for a machine would set "autoMount: ''", but that was a sledgehammer solution, especially when the goal was merely to prevent a diskette from being loaded in drive A; the preferred solution now is to set "autoMount: A: None", allowing the rest of the machine's autoMount settings, if any, to remain intact) 2017-06-17 21:30:03 -07:00
3.10 Fixed autoMount overrides (formerly, machines that wanted to override the diskette autoMount settings for a machine would set "autoMount: ''", but that was a sledgehammer solution, especially when the goal was merely to prevent a diskette from being loaded in drive A; the preferred solution now is to set "autoMount: A: None", allowing the rest of the machine's autoMount settings, if any, to remain intact) 2017-06-17 21:30:03 -07:00
3.11 Disk manifest updates 2017-06-02 09:22:27 -07:00
win95 Fixed autoMount overrides (formerly, machines that wanted to override the diskette autoMount settings for a machine would set "autoMount: ''", but that was a sledgehammer solution, especially when the goal was merely to prevent a diskette from being loaded in drive A; the preferred solution now is to set "autoMount: A: None", allowing the rest of the machine's autoMount settings, if any, to remain intact) 2017-06-17 21:30:03 -07:00
wincomm Bumped next release version to 1.35.0 2017-06-01 15:35:25 -07:00
README.md Cutting back on the number of redirects (attempting to reduce Jekyll build time) 2017-02-09 13:59:24 -08:00
win10x.xml Numerous changes to make paper tape configurations more consistent with disk configurations. This allows all devices to share the machine-wide "autoMount" configuration object, now that the PC11 has a proper device name ("PTR"), making its properties distinguishable from those for RK11 and RL11 drives (eg, "RK0", "RL0", etc). And all the tape/disk components now use "Load" functions to connect a tape or disk to a device ("Attach" is deprecated). And finally, all tape/disk components now support operations to deposit their media directly into memory -- although in this case, the names of the operations are necessarily different: "Read" for tape images, "Boot" for disk images. The difference is partly historical convention but also reflects the fact that a "Boot" operation is more limited: paper tapes were designed to be completely loaded into memory, whereas bootable disks are designed for only the first sector to be loaded and executed. Also, paper tape images are now flagged as non-auto-starting, because they often require some user action (eg, loading another tape, setting some switches, etc), whereas disk boot sectors are flagged as auto-starting (see the fStart parameter of the loadImage() interface in the RAM component). 2016-12-03 14:49:51 -08:00

README.md

layout title permalink
page Microsoft Windows /disks/pcx86/windows/

Microsoft Windows

Information is available for assorted versions of Microsoft Windows: