VOGONS


First post, by James_Richards

User metadata
Rank Newbie
Rank
Newbie

So,, I came into possession of a good chunk of old games. the original owner must have either been a collector or just into Infocom and Epyx games.
To make these work with DOSBox I believe there is a special way to archive the disks. to an image file format. For now, I pursued a couple sites with that already done and downloaded a couple for testing. (my floppy drive is dead at the moment) PCJr and booter games from the era are well before I was old enough to use a computer. Most of my experience is with 286 and some rusty "I remember how to do that" moments with Commodore64.
No Amiga experience whatsoever.

For DOSBox, I know how to mount folders to acta as HDD or FDD. So that isn't an issue. I haven't toy'd around with booting images, though.
If I understand this correctly;
I have to IMGMOUNT a floppy image BEFORE I can BOOT it?
I WAS trying to just throw the command;

BOOT ".\DISK.IMG" -l A

but that kept failing.
I HAVE to

IMGM OUNT A ".\DISK.IMG" -t floppy

first?

The goal now, is through a series of batch menus to make it easy to load games for my cousin's kids. They have been watching me play these older games and are really curious.
A series of batch menus I made calls a game by going to it's directory

CD \GAME1 

then

CALL GAME1.BAT

I have things setup pretty well and have about 100 games already structured as I like, making it a kind of template approach as I devour the rest of my collection and digitize it along with any freeware releases

Do I have it right that I need to IMGMOUNT the booter floppy then call a BOOT on that mounted drive letter? then just call

IMGMOUNT -u A

once the game is quit to keep things from bungling for the next game or maybe get into the habit of unmounting the drive before mounting another image? I am trying to have this as one seamless thing so the kids don't have to reopen DOSBox.

...this could be fun...

Reply 1 of 10, by jmarsh

User metadata
Rank Oldbie
Rank
Oldbie
James_Richards wrote on 2024-06-13, 20:08:
then just call […]
Show full quote

then just call

IMGMOUNT -u A

once the game is quit to keep things from bungling for the next game or maybe get into the habit of unmounting the drive before mounting another image? I am trying to have this as one seamless thing so the kids don't have to reopen DOSBox.

Unfortunately there's no way around restarting DOSBox, once you run the BOOT command - it's the same as a regular PC, if you boot into another OS there's no way back without resetting.

Reply 2 of 10, by James_Richards

User metadata
Rank Newbie
Rank
Newbie

hmmmm...maybe some nifty scripting on my end then... And booter games are probably not able to be copied to "HDD" for "hard disk install" like some other games I have? the whole point of "booter'? Looking at mobygames, a couple of these look to have never been released on DOS

...this could be fun...

Reply 3 of 10, by wbahnassi

User metadata
Rank Oldbie
Rank
Oldbie

Some booter games got patched to have a DOS launcher if that suits you better.

Turbo XT 12MHz, 8-bit VGA, Dual 360K drives
Intel 386 DX-33, TSeng ET3000, 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 4 of 10, by Errius

User metadata
Rank l33t
Rank
l33t

BOOT is for bootable disks, which often don't have a DOS filesystem. IMGMOUNT is for DOS disks and won't work with most bootables. Typically you would use one or the other, not both.

What error message do you get when you run BOOT DISK.IMG -L A ?

(Note that BOOT, MOUNT and IMGMOUNT look for images (1) in the DOSBox root directory, (2) in the DOSBox program directory. Relative paths are relative to these two locations.)

Is this too much voodoo?

Reply 5 of 10, by wierd_w

User metadata
Rank Oldbie
Rank
Oldbie

I've always used imgmount with the '-fs none' option for nondos disks. As long as it has the correct number of sectors, it doesnt matter.

'Boot [imagefile and path]' screws up way too often in my experience. There seems to be a real difference of some kind in how the disk is handled by dosbox.

Also, I almost always give full system paths for images anyway.

My .02$ worth anyway.

Reply 6 of 10, by James_Richards

User metadata
Rank Newbie
Rank
Newbie
Errius wrote on 2024-06-13, 23:03:
BOOT is for bootable disks, which often don't have a DOS filesystem. IMGMOUNT is for DOS disks and won't work with most bootable […]
Show full quote

BOOT is for bootable disks, which often don't have a DOS filesystem. IMGMOUNT is for DOS disks and won't work with most bootables. Typically you would use one or the other, not both.
(yeah, 98% of my experience and knowledge is based on DOS starting with the 386 I built out of spares back in 1994 I was only 12 years old!)
What error message do you get when you run BOOT DISK.IMG -L A ?
(I wasn't keeping good notes, just that it couldn't boot.) I first tried BOOT disk.img -l a (the a drive was no mounted or IMGMOUNTed at the time.
I read the wiki and it seemed from the info that it had to be IMGMOUNTed first. THAT worked.
If I just use BOOT disk.img -l a, I get "unable to boot off of drive A"
No errors about opening the image, so the assumption is the img is good.
IMGMOUNTING it first worked.
The test image is Infocom's text adventure Cutthroats
(Note that BOOT, MOUNT and IMGMOUNT look for images (1) in the DOSBox root directory, (2) in the DOSBox program directory. Relative paths are relative to these two locations.)

I understand the relative paths to the working directory of dosbox. I got into the habit as it is easy to organize and makes it somewhat portable. Like my father, who is now retired and has free time again and wants to play some games we got in the mid 90's that he never finished or just wants to play for nostalgia. I made a directory he could easily get off my file server (no longer have due to a cat jumping on it and knocking it over. Ever experience the terror of 6 x 8TB RAID platter drives hitting the floor, which housed a carefully maintained movie and music server, local file server intended as a digital store of all my physical media. VHS rips, DVD rips, sourcecode snippets for a game I was star ting to actually make into something. 🙁

example;
D:/
├─ DOSBox/
│ ├─ dosbox.exe
│ ├─ dosbox.conf
├─ C_HDD/
GAME1/
GAME1.EXEorBATorCOM
I can easily 7zip the GAME1 folder and delete it, free up some space and copy the 7zip to a large 12TB platter drive I have to store and free up space on the SDD I use for modern games and everyday use. this way I can juast decompress the folder into the C_HDD folder and ready to ply instead of mounting images and going though the install process every time I want to play "that one game".

I plan on the same with booter images.
So, what works for me, unless a future problem can be seen, is this:
In the C_HDD folder, I have

BOOTER GAME/
├─ GAME.BAT
├─ disk_a.img
├─ disk_b.img

GAME.BAT contents
IMGMOUNT -u a **ensures A is available
IMGMOUNT -u b **ensures B is available
IMGMOUNT A ".\disk_a.img" -t floppy **game disk A or booter
IMGMOUNT A".\disk_b.img" -t floppy ** game disk B or save file disk
BOOT -l a boots game
Using the same Cutthroats booter image as mentioned;
This, so far works. It allows me to reference in my batch menus to see that game's BAT and follows my current folder organization practices.
So far, I need to just find a way to restart DOSBox or start it back up when the game quits to go back to the batch menus. That I am sure I can figure out.
Not sure where to begin as the test booter I am using is an infocom text adventure and doesn't "drop to a shell" like games I am familiar with
As this "works" I can run that BAT and it mounts the images, then boots off A, plays the game, ;lets me save progress
I shut down DOSBox anf run the BAT again and I am able to resume my progress as the game saves to the B drive/image

I just originally thought BOOT was enough. relative or direct paths to the img file didn't work.

I even used a boot image for DOS and it wouldn't BOOT till I IMGMOUNTed it first. That image IS good, tested on real floppy writer on real a couple real machines.

...this could be fun...

Reply 7 of 10, by Errius

User metadata
Rank l33t
Rank
l33t

The problem is that the booter game will overwrite DOS in memory, so there's no way you can drop back to DOS.

The best solution is to find a DOS rip, as another poster suggested. These often have a quit option added by the ripper. (An example is the DOS rip of World Karate Championship, where you can press CTRL+X to quit to DOS. This obviously won't work in the original booter.)

Is this too much voodoo?

Reply 8 of 10, by James_Richards

User metadata
Rank Newbie
Rank
Newbie

mmmm. Then time for some googling. no idea where to find those things. Having a tough time finding floppy images of my much older games

The advice and infos is helpful! at least i sorted it out for myself ease of use for the kiddos is another matter. I would build a machine, but then I would build another and another. 🤣

...this could be fun...

Reply 9 of 10, by wbahnassi

User metadata
Rank Oldbie
Rank
Oldbie

We can't point you here. Booter game patches for DOS often were made to bypass the game's copy protection. Some sites offer playing such games online via web DosBox, and a few allow downloading the files... at your own risk of course (viruses and all).

Turbo XT 12MHz, 8-bit VGA, Dual 360K drives
Intel 386 DX-33, TSeng ET3000, 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 10 of 10, by jmarsh

User metadata
Rank Oldbie
Rank
Oldbie

Note that there is a keybind for restarting DOSBox, I think by default it is set to ctrl+alt+home.