VOGONS


First post, by senrew

User metadata
Rank Oldbie
Rank
Oldbie

I'm at a loss for how to get past a couple of problems with my DOS rig.

I'm running:
Aopen AX59pro SS7 MB, MVP3 chipset
P200mmx
128MB RAM
Diamond Stealth 4000
Voodoo 1

I have two partitions, one with pure dos 6.22 and Win95 installed to a seperate partition.

Issue 1:
I originally tried to get this to work with a vortex2 cartd with a xr385 daughterboard, but at the driver installation for the card, it will just hang up when installing the gameport driver. From what I could find online, the vortex cards have issues with MVP3 boards running AGP video and PCI audio. They recommended installing the latest 4-in-1 drivers. I installed DOS, then win95, then the VIA drivers, then video, then the Vortex drivers. I rebooted between each driver. The Vortex drivers install, then you must reboot so that it can identify each component. When it gets to the gameport portion, it locks up and hangs.

Anyone experience this and have any clue around it? I said screw it and swapped out the vortex for my CT2490 with the daughterboard. I figure i can deal with the hanging notes until I get a better ISA card or figure out how to get around the vortex issue.

Which leads me to...

Issue 2:
I've been fucking around with this rig for weeks now. Sometimes, after making changes, upon reboot, the machine will hang at the point between checking for a bootable CD, and booting from the hard drive. It will show it didn't find a bootable CD, and move on to the hard drive part, where it will just sit until I turn it off.

I had asked about this in another tread once, and was told to use smaller paritions or something due to using such a much newer hard drive on the older controller on this board.

I formatted it with DOS as it's going to be a DOS/Win95 machine only. It saw 8gb out of the 40gb drive, I made 4 partitions to use up all the space, 2/2/2/1.8 or something is how fdisk divided it up.

Anyway. I've tried fixing the mbr, and other such things, but once this happens, I have no way of booting from the hard drive. I can boot from CD or Floppy just fine. I've tried booting from a floppy and reversing whatever changes to the startup files I made just before the lock up but it still doesn't help.

Any suggestions? I'm really at the point were I want to just burn this rig to the ground and start over with a more predictable TX or VX board or something.

Halcyon: PC Chips M525, P100, 64MB, Millenium 1, Voodoo1, AWE64, DVD, Win95B

Reply 1 of 3, by senrew

User metadata
Rank Oldbie
Rank
Oldbie

Ok, after doing some more testing, I have a bit of an update on issue 2.

After detecting that there is no bootable cd in the drive, it'll query the floppy, and just sit there with the floppy light on searching for a disk. If I reboot with a disk in the drive, it boots up just fine from the floppy. Am I missing something here?

UPDATE:
So, I swapped the drive boot order in the bios; CD -> C -> A. It hit the CD, didn't find a bootable disc, moved to the C drive and BAM, invalid system disk.

The last change I made was using the DOS SB installer.

So, my path with this version of the rig was: Partition hard drive; C,D,E,F. Install DOS to C. Install 95 to D, install VIA, Video, Audio (vortex) drivers. Swapped out vortex for the SB16. F4 boot to original OS (booted without issue). Installed SB16 DOS installers, CTCM, etc. Reboot. Lockup.

Did the SB changes screw up the boot files?

I'm thinking I should start from scratch. Install DOS, Install SB16 stuff. Install win95 then VIA and Video drivers and see where we go from there.

Halcyon: PC Chips M525, P100, 64MB, Millenium 1, Voodoo1, AWE64, DVD, Win95B

Reply 2 of 3, by pyrogx

User metadata
Rank Member
Rank
Member

About the vortex issue: You can disable the gameport and prevent win95 from detecting it:
- copy the vortex2 drivers to your harddisk
- edit the file AU30MMED.INF
- search for a section called "AspenOverides.AddReg"
- uncomment the line "HKR,Config,DisableJoystick,1,1"
- save, remove all traces of the original vortex2 driver in the Windows directory (Don't forget C:\WINDOWS\INF)
- let win95 redetect the Vortex and point it to the modified driver

I have no specific idea about your HD problem, but I too had some issues when installing DOS and win95 on the same harddisk if both OSs had a primary partitiion for themselves.
Some random thoughts:
What geometry translation did you select in BIOS (CHS, LBA)? Does the BIOS have an option to disable DMA or UltraDMA harddisk access? Maybe the boot failures are speed/DMA related.

Reply 3 of 3, by Malik

User metadata
Rank l33t
Rank
l33t

For the second problem :

Looks like the boot flag is missing. Dos and Win9x's FDISK can't set a non-primary partition as active. Boot with a DOS 6.22 boot disk. Check the contents of the "C:" drive. If it's the DOS partition, try entering "SYS C:", provided SYS.EXE file is in the boot disk, to transfer the system files to the C: drive. On which partition is your Win95 installed?

Or,

Try this:

1. Use a 3rd party partition manager to create 2 PRIMARY partitions. (Delete all partitions first and start from scratch.)

- MS-DOs's partition manager won't allow you to create 2 primary partitions on the same drive.

2. Reserve the first part of the partition with 8GB for DOS, at the beginning of the drive.

- here, you can do one of two methods :

i. Only reserve the first 8GB space and create the parttions after installing Win95, or,
ii. Create partitions for DOS in the 8GB space, and then "HIDE" the partitions using the partition manager.

This is to make way to install Windows 95 first.

3. Create the rest of the space to create a FAT32 partition, provided you're installing a FAT32-supported version of Windows95.

Install Windows 95.

4. After installing Windows 95, and after completing all reboots and making sure Win95 is working well, now either

i.-Create the partitions for DOS in the first segement of the reserved space, or
ii.-Unhide all partitions.

When creating the DOS partitions, continue as you have made before, i.e. - 1st partition is primary and the rest are created in extended logical partitions.

If you're planning to hide and unhide, you can even use DOS' FDISK to create the partitions first, hide all partitions with a 3rd party partitioner and use the Win95's FDISK to create another Primary Partition with the FAT32 format. The hidden partitions will be shown as Non-Dos and FDISK will permit to create a primary partition.

After completing Windows 95 installation and all the reboots, you can then unhide the DOS partitions.

Once this is done, you can use the FDISK in either program, to "SET ACTIVE PARTITION", to boot into either partition. When in DOS, and you would like to boot into Win95, use the FDISK in DOS and vice versa in Win95.

By using a FAT32 partition for Win95, the DOS utilities like defrag and chkdsk won't mess up with the Win95 files, since the DOS 6.22 can't "see" a FAT32 partition.

Finally, you can try using Boot Managers if you don't want to mess with partitions. e.g. - Smart Boot Manager, PLOP boot manager.

5476332566_7480a12517_t.jpgSB Dos Drivers