jejenkin@nmsu.edu (JENKINS) (06/13/91)
I purchased MINIX v1.5 two days ago, and spent most of yesterday
morning installing it on my 286 PC. Upon completion of the installation,
I attempted to use the DOSXXX commands to grab some C code I wanted to
load up. I keep getting a message that says "unable to open /dev/dosA"
(or dosB or dosC, whichever drive I try to read from). The battery
of test programs supplied with MINIX ran and exectuted flawlessly; I am
entering the DOSDIR, READ, and WRITE commands exactly as stated in the
manual. Any clues as to what is going wrong here?? Pertinent info follows:
12 MHz 286 clone with AMI VLSI chipset
MS-DOS 3.30
Drive A: 1.2/360 5.25 floppy
Drive B: 1.44/720 3.5 floppy
Drive C: 85MB Harddisk
Partition 1: 32MB PRI-DOS
Partition 2: 32MB EXT-DOS
Partition 3: 1MB RAM image for MINIX
Partition 4: 20MB MINIX
This problem is most aggravating, since I am presently unable to port
or copy anything for MINIX from the ftp sites (all my comm software runs
under DOS). Please help!!!
One other item I have a question about while I'm posting, and that is the
ps command. When I press the F1 key, I get a listing of all the processes
that are currently running. When I type the ps command, I get some message
about being unable to open some kernal file. Have I somehow botched the
installation??
Please reply E-mail if possible, to jejenkin@dante.nmsu.edu
Thanks again,
Jeff Jenkinsasg@sage.cc.purdue.edu (The Grand Master) (06/14/91)
In article <1516@opus.NMSU.Edu> jejenkin@nmsu.edu (JENKINS) writes: } } I purchased MINIX v1.5 two days ago, and spent most of yesterday }morning installing it on my 286 PC. Upon completion of the installation, }I attempted to use the DOSXXX commands to grab some C code I wanted to }load up. I keep getting a message that says "unable to open /dev/dosA" }(or dosB or dosC, whichever drive I try to read from). The battery }of test programs supplied with MINIX ran and exectuted flawlessly; I am }entering the DOSDIR, READ, and WRITE commands exactly as stated in the }manual. Any clues as to what is going wrong here?? Pertinent info follows: }12 MHz 286 clone with AMI VLSI chipset }MS-DOS 3.30 Do the following ln /dev/fd0 /dev/dosA ln /dev/fd1 /dev/dosB ln /dev/hd1(or whatever your dos HD partition is) /dev/dosC then try again and it will work culater Bruce --------- ### ## Courtesy of Bruce Varney ### # aka -> The Grand Master # asg@sage.cc.purdue.edu ### ##### # PUCC ### # ;-) # # ;'> # ##
feustel@netcom.COM (David Feustel) (06/14/91)
I don't think the DOS commands work with DOS 3.3 extended partitions. -- David Feustel, 1930 Curdes Ave, Fort Wayne, IN 46805, (219) 482-9631 EMAIL: feustel@netcom.com or feustel@cvax.ipfw.indiana.edu
kjh@pollux.usc.edu (Kenneth J. Hendrickson) (06/14/91)
In article <1991Jun13.181843.9056@netcom.COM> feustel@netcom.COM (David Feustel) writes: >I don't think the DOS commands work with DOS 3.3 extended >partitions. They do on my machine. I've heard a rumor that they don't work with DOS 4.0 16-bit partitions, but that they work fine with all 12-bit partitions. -- favourite oxymorons: student athlete, military justice, mercy killing Ken Hendrickson N8DGN/6 kjh@usc.edu ...!uunet!usc!pollux!kjh
ns@csd.cri.dk (Nick Sandru) (06/24/91)
asg@sage.cc.purdue.edu (The Grand Master) writes: >In article <1516@opus.NMSU.Edu> jejenkin@nmsu.edu (JENKINS) writes: [...] >}I attempted to use the DOSXXX commands to grab some C code I wanted to >}load up. I keep getting a message that says "unable to open /dev/dosA" >}(or dosB or dosC, whichever drive I try to read from). >Do the following >ln /dev/fd0 /dev/dosA >ln /dev/fd1 /dev/dosB >ln /dev/hd1(or whatever your dos HD partition is) /dev/dosC >then try again and it will work I did it too, but when I tried to use DOSXXX from a non-privileged login, it failed. I had to set DOSXXX as setuid root. >culater > Bruce >--------- > ### ## >Courtesy of Bruce Varney ### # >aka -> The Grand Master # >asg@sage.cc.purdue.edu ### ##### # >PUCC ### # >;-) # # >;'> # ## Nick Sandru -- .signature waiting at the entry signal
grundy@rtf.bt.co.uk (Martin Grundy) (06/25/91)
In article <ns.677767081@csd> ns@csd.cri.dk (Nick Sandru) writes: > [some deletions] >I did it too, but when I tried to use DOSXXX from a non-privileged login, >it failed. I had to set DOSXXX as setuid root. > >Nick Sandru > Check the permissions/owner on /dev/fd0 etc. If the owner is bin or root and the permissions are set to -rw------, there's your problem. Do:- chmod 666 /dev/fd? to allow "world" to read/write. ----------------------------------------------------------------- Martin Grundy | email: grundy@rtf.bt.co.uk British Telecom Customer Systems | Hyperion House | phone: +44 273 762102 96-99 Queens Road | fax: +44 273 722038 or Brighton BN1 3XF. | +44 273 762071 (netfax)
ns@csd.cri.dk (Nick Sandru) (06/25/91)
In info-minix you write: [... stuff on DOSXXX not working] >Check the permissions/owner on /dev/fd0 etc. >If the owner is bin or root and the permissions are set to -rw------, >there's your problem. Do:- > chmod 666 /dev/fd? >to allow "world" to read/write. The problem is that I share the system with a couple of friends, who don't have too much Unix knowledge. So I preferred to maintain the restricted permissions and make DOSXXX setuid root, in order to avoid possible disasters (/dev/hd1 is an MS-DOS partition). >----------------------------------------------------------------- >Martin Grundy | email: grundy@rtf.bt.co.uk >British Telecom Customer Systems | >Hyperion House | phone: +44 273 762102 >96-99 Queens Road | fax: +44 273 722038 or >Brighton BN1 3XF. | +44 273 762071 (netfax)