I have been attempting to make a DOS boot drive read-only with a driver but can't find such a driver to do it. I was told a long time ago its possible to make any hard drive within dos read-only with a driver but just can't find such a driver. I know its possible using grub4dos with map --read-only (hd0) (hd0) and than chainloader /io.sys. But for reasons I don't want to to use this method. There has to be another away to make DOS think the drive is write protected with a driver, or another way.
make a DOS boot drive read only with driver or other way
#1
Posted 08 May 2018 - 02:16 AM
#2
Posted 08 May 2018 - 04:54 AM
if you boot from a medium with dos, must be there a modification command.com with usb-informations
or an "device".sys file where it is load in config.sys as tsr file where makes ro the system-partition
with maybe switches like "LOADHIGH blabla.sys /syspart=ro" to hold it ro and the other possibility an autorun.exe for win/nt ot at the sdcard the switch by side of the hardware to switching ro
best regards
Blacky
#3
Posted 08 May 2018 - 01:45 PM
if you boot from a medium with dos, must be there a modification command.com with usb-informations
or an "device".sys file where it is load in config.sys as tsr file where makes ro the system-partition
with maybe switches like "LOADHIGH blabla.sys /syspart=ro" to hold it ro and the other possibility an autorun.exe for win/nt ot at the sdcard the switch by side of the hardware to switching ro
best regards
Blacky
I am trying to make a real IDE hard drive read-only , not anything usb
#4
Posted 10 May 2018 - 07:41 AM
You can use grub4dos to load a DOS img\ima file into memory and run it from there.
Any changes you make during that session will be lost.
If you write-protect the drive, no files (even temporary files) can be created by DOS - is that what you want?
Must the IDE drive directly boot to DOS via PBR to IO.SYS? What 'reasons' do you have for not wanting to use grub4dos?
Just trying to find out if there is another way to skin the cat...
P.S. I have not tried this but may work under MS-DOS? .. http://help.fdos.org...se/fdshield.htm
Edited by steve6375, 10 May 2018 - 07:48 AM.
#5
Posted 11 May 2018 - 05:28 PM
Another semi-random idea.
What would happen with an image of a CD-ROM set to "hard disk emulation"?
Still booting to grub4dos would be needed, though.
If there is any actual reason NOT to use grub4dos there are other possible booting mechanisms (Syslinux/memdisk), once - one way or the other - a DOS has been loaded there are a number of DOS Ramdisks (Frank Uberto's one comes to mind, but also SRDISK might do) and one of the various drivers by Jason Hood:
http://adoxa.altervista.org/shsucdx/
might well do, still the issue is the initial loading (before the driver mounts the image).
Another possible tool could be NTFSDOS, a driver of which two versions exist, one (free) which is read-only and one (not anymore available, Commercial) that had both read and write capabilities:
https://web.archive....es/NtfsDos.html
here the read-only is at (NTFS) volume level (NOT at physical disk level) though.
Wonko
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users