dave@dptechno.uucp (Dave Lee) (07/10/90)
Help! I'm having problems getting a unix and dos partition to coexist on my second hard drive. I setup my second drive with sysadm/addharddisk. I partitioned as follows: Drive 68M RLL -- fdisk info Partition type start end length ----------------------------------------------- 1 unix 1 530 530 2 dos 531 1022 492 Mounted a /users file system on the 1st partition, coppied some files, and unmounted /users. Booted 4.0 dos stand alone and formated the dos partition. Rebooted unix, ran vpix with the following line in vpix.cnf D /dev/dsk/1p0 Coppied a full dos file system (30M) of files to the D: drive with vpix. Exited vpix and tried to mount /users. It wouldnt mount. Fsck fails. mkpart -t v disk01 says : Warning - invalid pdinfo block found -- initializing. mkpart -t p disk01 reports no partitions. Remade the partition info and remade the file system for /users, coppied some data to /users, and zap goes D:, directory structure thrashed. Whats going on here? Is this just vpix? The FM says that the "D /dev/dsk/.." type of disk access is not the prefered method, Is that because it overwrites the unix vtoc table ? My first drive has a dos partiton and works fine (so far). However, it is the first partition. Do DOS partitions have to be first ? Also, the DOS partition on the first drive (installed automatically by the install process), was created starting at sector 0, not 1. The Fine Manual says you should skip sector 0, yet it works fine -- so far ;-) I've RTFM'd 'till the cows came home, but am still stuck. Thanks. Please Email, or post if you really want to. -- Dave Lee uunet!dptechno!dave
tikku@samsung.COM (Sanjay Tikku) (07/11/90)
dave@dptechno.uucp (Dave Lee) writes: >Help! I'm having problems getting a unix and dos partition to coexist on >my second hard drive. I setup my second drive with sysadm/addharddisk. >I partitioned as follows: > Drive 68M RLL -- fdisk info >Partition type start end length >----------------------------------------------- >1 unix 1 530 530 >2 dos 531 1022 492 Primary DOS partition has to be the 1st parttition. I haven't experimented but I would guess that DOS partitions have to come ahead of non-DOS partitions. I too had strange problems when Unix was on the 1st partition but they all vanished once I put DOS partition as the 1st one on the disk. sanjay -- Sanjay Tikku |Voice: 508-685-7200ext.123 Samsung Software America, Inc. |FAX: 508-685-4940 One Corporate Drive |Internet: tikku@samsung.com Andover, MA 01810 |UUCP: ...uunet!samsung!tikku
darryl@ism780c.isc.com (Darryl Richman) (07/12/90)
In article <532@dptechno.UUCP> dave@dptechno.uucp (Dave Lee) writes:
"Help! I'm having problems getting a unix and dos partition to coexist on
"my second hard drive. I setup my second drive with sysadm/addharddisk.
"I partitioned as follows:
" Drive 68M RLL -- fdisk info
"Partition type start end length
"-----------------------------------------------
"1 unix 1 530 530
"2 dos 531 1022 492
"
"Mounted a /users file system on the 1st partition, coppied some files,
"and unmounted /users. Booted 4.0 dos stand alone and formated the dos partition.
"Rebooted unix, ran vpix with the following line in vpix.cnf
"
"D /dev/dsk/1p0
This is your problem. 1p0 is the *entire* second disk. You probably want
to use 1p2.
--Darryl Richman
--
Copyright (c) 1990 Darryl Richman The views expressed are the author's alone
darryl@ism780c.isc.com INTERACTIVE Systems Corp.-A Kodak Company
"For every problem, there is a solution that is simple, elegant, and wrong."
-- H. L. Menckenkeithe@tekgvs.LABS.TEK.COM (Keith Ericson) (07/12/90)
In article <532@dptechno.UUCP> dave@dptechno.uucp (Dave Lee) writes: >Help! I'm having problems getting a unix and dos partition to coexist on >my second hard drive. I setup my second drive with sysadm/addharddisk. >... >Mounted a /users file system on the 1st partition, coppied some files, >and unmounted /users. Booted 4.0 dos stand alone and formated the dos >partition. Last I knew VP/ix was compatible with DOS 3.3-created disk drives; the DOS 4.01 may be the reason nothing works... kEITHe
rmf@media.uucp (Roger Fujii) (07/13/90)
darryl@ism780c.isc.com (Darryl Richman) writes: >In article <532@dptechno.UUCP> dave@dptechno.uucp (Dave Lee) writes: >"Help! I'm having problems getting a unix and dos partition to coexist on >"my second hard drive. I setup my second drive with sysadm/addharddisk. >"I partitioned as follows: >" Drive 68M RLL -- fdisk info >"Partition type start end length >"----------------------------------------------- >"1 unix 1 530 530 >"2 dos 531 1022 492 >" >"Mounted a /users file system on the 1st partition, coppied some files, >"and unmounted /users. Booted 4.0 dos stand alone and formated the dos partition. >"Rebooted unix, ran vpix with the following line in vpix.cnf >" >"D /dev/dsk/1p0 >This is your problem. 1p0 is the *entire* second disk. You probably want >to use 1p2. I don't think so. VPIX 1.1.1 has no clue about partitions. As far as I can figure, drive D *MUST* b /dev/dsk/xp0. This is due to the fact that VPIX apparently looks for the boot record for drive D which partitions do not have. Now, a 'extended' partition looks like a 'boot' disk, but for some inexplicable reason, any logical drives after the first one does not 'attach' correctly. In summary: using D is a lose if: 1) you have a partition > 32M 2) If this is not the FIRST "disk" in the partition. (this may be gotten around, but I couldn't find it). Also, using the UNIX utilities to prep up the DOS side would probably help. -- Roger Fujii - Media Cybernetics Phone: (301)495-3305 Internet: rmf%media@uunet.uu.net UUCP: {uunet,hqda-ai}!media!rmf
root@usaos.UUCP (SSG W.D. Calhoun (postmaster)) (07/13/90)
In article <7785@tekgvs.LABS.TEK.COM*, keithe@tekgvs.LABS.TEK.COM (Keith Ericson) writes: * In article <532@dptechno.UUCP* dave@dptechno.uucp (Dave Lee) writes: * *Help! I'm having problems getting a unix and dos partition to coexist on * *my second hard drive. I setup my second drive with sysadm/addharddisk. * *... * *Mounted a /users file system on the 1st partition, coppied some files, * *and unmounted /users. Booted 4.0 dos stand alone and formated the dos * *partition. * * Last I knew VP/ix was compatible with DOS 3.3-created disk drives; * the DOS 4.01 may be the reason nothing works... I run 386/ix 2.0.2 and VP/ix 1.1.1 and I have no problem running a DOS 4.01 created partition (<32m) mounted with: mount -f DOS /dev/dsk/0p1 /dos /dos being the directory I created as a mount point. My DOS partition is the first partition on the drive and starts at sector 0. I have not tried with DOS as the second or subsequent partition or with partitions larger than 32m. As a sideline, the VP/ix users manual does say that on way to access a DOS partition is by placing a line: D /dev/dsk/0p0 in the vpix.cnf file. This did not work for me. I also recall that, as someone has already said, 0p0 refers to the entire 1st drive. The only problem that I had mounting the DOS partition directly was that I was running out of DOS inodes but a fix listed in the frequently asked questions posting seems to have taken care of that. --- W.D. Calhoun The U.S. Army Ordnance School at Fort Belvoir, VA calhoun%usaos@uunet.uu.net | uunet!usaos!calhoun
randyt@asdnet.uucp (Randy Terbush) (07/16/90)
In <45075@ism780c.isc.com> darryl@ism780c.isc.com (Darryl Richman) writes: >In article <532@dptechno.UUCP> dave@dptechno.uucp (Dave Lee) writes: >"Help! I'm having problems getting a unix and dos partition to coexist on >"my second hard drive. I setup my second drive with sysadm/addharddisk. >"I partitioned as follows: >" Drive 68M RLL -- fdisk info >"Partition type start end length >"----------------------------------------------- >"1 unix 1 530 530 >"2 dos 531 1022 492 >" Other follups correctly suggest that the DOS partition should be first. >This is your problem. 1p0 is the *entire* second disk. You probably want >to use 1p2. Wrong. The device name should be /dev/dsk/0p0. The release notes incorrectly state that you should use /dev/dsk/0p1. However, the VP/ix manual says that you need to use 0p0. I have noticed some peculiarities here: mount -f DOS /dev/dsk/0p0 /dos will not work. You must use 0p1 here. The 'D /dev/dsk/0p0' statement in vpix.cnf mounts the drive through VP/ix. You CANNOT do both. -- Randy Terbush - Advanced System Design - Boise, Idaho - Voice +1 208 342 0835 UUCP: asdnet!randyt --------------------- UNIX Workstation Design and Support INET: asdnet!randyt@sunstone.idbsu.edu -- CAD Graf*ix BBS --- +1 208 342 8541
keithe@tekgvs.LABS.TEK.COM (Keith Ericson) (07/17/90)
In article <110@usaos.UUCP> root@usaos.UUCP (SSG W.D. Calhoun (postmaster)) writes: }In article <7785@tekgvs.LABS.TEK.COM*, I wrote: }* }* Last I knew VP/ix was compatible with DOS 3.3-created disk drives; }* the DOS 4.01 may be the reason nothing works... }* To which a response came: }I run 386/ix 2.0.2 and VP/ix 1.1.1 and I have no problem running a DOS 4.01 }created partition (<32m)... This, the "<32m," is probably the difference: I'd used DOS4.01 specifically because I _wanted_ more DOS space and had created a 200 megabyte DOS partition. Thanks for the followup! kEITHe
dave@dptechno.uucp (Dave Lee) (07/18/90)
Thanks to all who responded to question concerning DOS partitions.
Here is a summary of what to do to use DOS partitions for DOS,
VPIX, and unix "mount -f DOS". My objective here is to have a system
that appears as similar as possible running under DOS standalone,
and VPIX. Considering the amount of incorrect responses I recieved,
(especially from folks as ISC) I thought this would be of general interest.
Hard Drive Info:
Drive 0 108 RLL
Drive 1 68 RLL
A1) BACKUP EVERYTHING YOU COULD POSSIBLY THRASH !!!!
A2) BACKUP EVERYTHING ELSE !!!!
A3) BACKUP YOUR BACKUPS ;-)
1) When installing ISC, create a small DOS partition as the first partition.
I made a 10M partition. This will become your C: drive for:
DOS standalone
UNIX dossette commands.
Format this partition from a floppy booted DOS. FORMAT C: /s
MAKE SURE that it is < 32 M.
Place only files on C: that will be useless under VPIX.
These include the \DOS directory, and any programs that do things VPIX
hates like scanner programs, Protected mode programs, Modem programs etc.
2) Use sysadm -- addharddisk menu to install the second drive.
Make a DOS partition < 32 M as the FIRST partition.
I suggest starting at cylinder 2. the FM in one place says to skip
cylinder 0, and in another place to skip 0 and 1. Just to be safe,
I skip 0 and 1.
This will become drive D: for
DOS standalone
UNIX dossette commands
VPIX <optional>
Format D: from a bootable DOS disk.
Place the rest of your DOS files on D:
3) If you want to mount your dos drives (C:, or D:) you should apply the
fixes posted earlier adjusting NDOSINODE and remake the kernal.
To mount the dos files use
mount -f DOS /dev/dsk/Xp1 /dos
where X is the drive number (0 or 1).
If you want to use drive D: from vpix edit your vpix.cnf file to say
D /dev/dsk/1p0
Which magically accesses the DOS partition on your first hard drive,
rather than your entire hard drive as one might expect.
Remember to allow read/write permission to /dev/dsk/1p0.
If you dont like that you cant have a drive D:, but you can use
Z:\dos to access your dos files it is mounted as above.
NOTES:
NEVER make the DOS partition anything but the FIRST partition.
HORRIBLE things happen if you make the DOS partiton second.
dossette seems to be the most versatile program. It can use DOS
partitions > 32 M. VPIX and mount -f can only access < 32M
filesystems.
Contrary to popular oppinion ;-) DOS 4.x filesystems seem to work
fine under vpix and mount, providing they are < 32 M.
Give your new setup a FULL STOMPING before trusting it.
Make sure you can mount and unmount ALL filesystems, fill them
up to the brim with data, delete it, and make sure ALL filesystems
still work.
It is possible for you disk to be so completely trashed that you
have to do a LOW LEVEL format if you mess up.
My 68M drive got so bad that even the ISC Boot Disk would panic.
I had to go to the ROM DIAGNOSTICS format to fix the problem.
THE GOOD PART:
With the above procedures, I can now have a fairly consistant
enviroment under VPIX and DOS.
For me this is very important. Some programs are extremely
difficult to change their installation drives or directories.
In particular Wordstar 2000 uses a binary configuration file
that has full pathnames (like C:\WS2000\WS2.EXE) with no easy
way to modify it. I had to use norton utils to change the
"C:" to a "D:" when I moved the directory tree.
This would be a real pain if I had to use different drive
letters running DOS standalone and vpix.
Disclaimer:
This is based on my own personal experiences (trauma ;-)) and
other's suggestions (Email and Posting) and contridicts some
statements earlier made in this newsgroup.
It works for me, and it should work for you, but I dont guarentee it.
Please BACKUP EVERYTHING to save hairpulling and foul language
in case of errors or typos.
If anyone dissagrees with any of the above, please Email or Post.
--
Dave Lee
uunet!dptechno!davejohn@jwt.UUCP (John Temples) (07/20/90)
In article <7811@tekgvs.LABS.TEK.COM> keithe@tekgvs.LABS.TEK.COM (Keith Ericson) writes: >In article <110@usaos.UUCP> root@usaos.UUCP (SSG W.D. Calhoun (postmaster)) writes: >}I run 386/ix 2.0.2 and VP/ix 1.1.1 and I have no problem running a DOS 4.01 >}created partition (<32m)... > >This, the "<32m," is probably the difference: I'd used DOS4.01 specifically >because I _wanted_ more DOS space and had created a 200 megabyte DOS partition. Along the same lines, has anyone had any success at getting large DOS partitions working with VP/ix? Can VP/ix be made to work with DOS 4.01 and large partitions? I have booted 4.01 from a floppy with vpix -b, then done a SYS C:, and got a working VP/ix that comes up in 4.01. But things like DOSMOUNT no longer work, so the UNIX file system can't be accessed. I also tried using DOS partitioning software (DMDRVR from OnTrack). VP/ix will load the driver, and I can do a directory on the large partition; but the contents of all subdirectories appear garbled. Is there some other partitioning software that works under VP/ix? Or is this simply a limitation in VP/ix than can't be overcome? -- John W. Temples -- john@jwt.UUCP (uunet!jwt!john)