VOGONS


First post, by Rolo_Ranger

User metadata
Rank Newbie
Rank
Newbie

I seem to be having an issue.

Everything runs fine - 6.22 and Win 3.11 boot without issue at startup.
But once I try exiting windows back into DOS i get nothing but a blinking underscore in the top left.

I tried running memmaker after windows install to see if that'd do anything. No luck.

Has anyone else had this issue before?

Reply 1 of 8, by wbahnassi

User metadata
Rank Oldbie
Rank
Oldbie

Yes it happened to me and I'm trying to recall when..
Is it by any chance installed on a FAT32 or is running from a Win95+MSDOS setup?

Turbo XT 12MHz, 8-bit VGA, Dual 360K drives
Intel 386 DX-33, Speedstar 24X, SB 1.5, 1x CD
Intel 486 DX2-66, CL5428 VLB, SBPro 2, 2x CD
Intel Pentium 90, Matrox Millenium 2, SB16, 4x CD
HP Z400, Xeon 3.46GHz, YMF-744, Voodoo3, RTX2080Ti

Reply 2 of 8, by BitWrangler

User metadata
Rank l33t++
Rank
l33t++

Have you messed around with mono graphics or copied this windows install from another machine?

It may be that it is returning to the wrong DOS text mode. In that it is returning to a DOS prompt, just not on the hardware you are looking at. Give it a bit until all disk activity seems to have stopped, then type
mode co80
blind at the prompt, press return and see if you get back.
Also if the windows install didn't come off generic disks check you haven't got a win.bat file in your path running win then putting a mode mono in after so it is trying to return to mono.

Unicorn herding operations are proceeding, but all the totes of hens teeth and barrels of rocking horse poop give them plenty of hiding spots.

Reply 3 of 8, by Rolo_Ranger

User metadata
Rank Newbie
Rank
Newbie
wbahnassi wrote on Yesterday, 17:30:

Yes it happened to me and I'm trying to recall when..
Is it by any chance installed on a FAT32 or is running from a Win95+MSDOS setup?

No, it was a (supposedly) fresh msdos install with Fat16 (albeit, from many years ago)

BUT I see that FDisk /status is reporting back

Disk    Drv    MBytes    Free    Usage
1 16 0 100%
C: 503

and FDISK > selection 4 shows:

Partition    Status    Type           Volume    Label    MBytes    System    Usage
C:1 A PRI DOS DOS 503 FAT16 100%

Total Disk Space is 16 MBytes

That seems odd.

Reply 4 of 8, by Rolo_Ranger

User metadata
Rank Newbie
Rank
Newbie
Rolo_Ranger wrote on Yesterday, 19:39:
No, it was a (supposedly) fresh msdos install with Fat16 (albeit, from many years ago) […]
Show full quote
wbahnassi wrote on Yesterday, 17:30:

Yes it happened to me and I'm trying to recall when..
Is it by any chance installed on a FAT32 or is running from a Win95+MSDOS setup?

No, it was a (supposedly) fresh msdos install with Fat16 (albeit, from many years ago)

BUT I see that FDisk /status is reporting back

Disk    Drv    MBytes    Free    Usage
1 16 0 100%
C: 503

and FDISK > selection 4 shows:

Partition    Status    Type           Volume    Label    MBytes    System    Usage
C:1 A PRI DOS DOS 503 FAT16 100%

Total Disk Space is 16 MBytes

That seems odd.

Seems something got screwed in the original install if it's only showing 16MB of total disk space.
I reckon a fresh start is probably best bet?

Reply 5 of 8, by BitWrangler

User metadata
Rank l33t++
Rank
l33t++

Possibly could happen like that if you partitioned with old version of DOS and did a format /s from newer MSDOS... orrr something. talking about the FAT12 FAT16 thing.

Unicorn herding operations are proceeding, but all the totes of hens teeth and barrels of rocking horse poop give them plenty of hiding spots.

Reply 6 of 8, by myne

User metadata
Rank l33t
Rank
l33t

Paste Autoexec.
Path?
Comspec?

I built:
Convert old ASUS ASC boardviews to KICAD PCB!
Re: A comprehensive guide to install and play MechWarrior 2 on new versions on Windows.
Dos+Windows 3.11+tcp+vbe_svga auto-install iso template
Script to backup Win9x\ME drivers from a working install
Re: The thing no one asked for: KICAD 440bx reference schematic

Reply 7 of 8, by Rolo_Ranger

User metadata
Rank Newbie
Rank
Newbie

I believe the issue stems back to my BIOS. I figured out why DOS FDISK was only reporting 16mb. My hard drive had like 1057 cylinders, MSDOS6.22 only understands up to 1024. My motherboard is pretty old for a 486 and does not appear to support LBA.

Wish I discovered this issue before i wiped everything! But I believe this was the root cause. I backed everything important up anyways.

Reply 8 of 8, by Jo22

User metadata
Rank l33t++
Rank
l33t++
Rolo_Ranger wrote on Today, 18:33:

I believe the issue stems back to my BIOS. I figured out why DOS FDISK was only reporting 16mb. My hard drive had like 1057 cylinders, MSDOS6.22 only understands up to 1024. My motherboard is pretty old for a 486 and does not appear to support LBA.

Wish I discovered this issue before i wiped everything! But I believe this was the root cause. I backed everything important up anyways.

1024 cylinders go from 0 to 1023
16 heads go from 0 to 15
63 sectors go from 1 to 63

It depends on the CMOS Setup, however, how the values are interpreted.
Maybe entering 1024 cylinders (total) or 1023 (0 to 1023) is the right thing to do. Same goes for heads (15 or 16).
To be on the safe side, better check the calculated storage capacity.
Entering 1020 cylinders, 16 heads, 63 should also work.

"Time, it seems, doesn't flow. For some it's fast, for some it's slow.
In what to one race is no time at all, another race can rise and fall..." - The Minstrel

//My video channel//