I don't think SHSUCDX is the command for loading CD images. Shouldn't it be the ones other than SHSUCDX itself, such as SHSUCDHD?

Here's the documentation for image handling tools (SHSUCDHD and some others).

I think what you want might be this, though I haven't really tried loading disk images myself as I haven't had such a need in DOS at the moment...
LH SHSUCDHD /F:"D:\CD IMAGES\SIMON_DOS\CD.ISO"

Though I think you might want to put your images in a path with short filenames and without whitespaces to avoid issues when loading the TSR. I wrapped your LFN path with double quotes but I'm not sure if it is the right way provided you have DOSLFN loaded.

I've never used shsucdhd but I believe it should be something like this:

LH SHSUCDHD /F:"D:\CD IMAGES\SIMON_DOS\CD.ISO"
LH SHSUCDX /D:SHSU-CDH

LSS10999 wrote on 2025-02-11, 05:58:

I don't think SHSUCDX is the command for loading CD images. Shouldn't it be the ones other than SHSUCDX itself, such as SHSUCDHD […]
Show full quote

I don't think SHSUCDX is the command for loading CD images. Shouldn't it be the ones other than SHSUCDX itself, such as SHSUCDHD?

Here's the documentation for image handling tools (SHSUCDHD and some others).

I think what you want might be this, though I haven't really tried loading disk images myself as I haven't had such a need in DOS at the moment...
LH SHSUCDHD /F:"D:\CD IMAGES\SIMON_DOS\CD.ISO"

Though I think you might want to put your images in a path with short filenames and without whitespaces to avoid issues when loading the TSR. I wrapped your LFN path with double quotes but I'm not sure if it is the right way provided you have DOSLFN loaded.

See, that was one of the things that confused me. I noticed that mentioned in another thread, but I don't seem to have any such file/driver. Nor did I see a command in the readme. I downloaded 3.09, which has Shsucdx.com and shcdx86.com. I don't believe I have DOSLFN. I take it that's an additional tool that allows longer file names? Thanks for the link to the documentation; I'll give it a look over. 😀

EDIT: Yeah, that was the same documentation I tried to decipher via the readme.

I think SHSUCDHD is from an older version then...? Judging from that linked documentation. That's 3.3, whereas I have 3.09. No such file is present.

DustyShinigami wrote on 2025-02-11, 15:13:

See, that was one of the things that confused me. I noticed that mentioned in another thread, but I don't seem to have any such file/driver. Nor did I see a command in the readme. I downloaded 3.09, which has Shsucdx.com and shcdx86.com. I don't believe I have DOSLFN. I take it that's an additional tool that allows longer file names? Thanks for the link to the documentation; I'll give it a look over. 😀

EDIT: Yeah, that was the same documentation I tried to decipher via the readme.

I think SHSUCDHD is from an older version then...? Judging from that linked documentation. That's 3.3, whereas I have 3.09. No such file is present.

The SHSUCDX 3.09 package contains only SHSUCDX.

There's a full package called SHSUCD 3-7 which includes everything including SHSUCDX 3.09. For loading images, this is the one you need.

LSS10999 wrote on 2025-02-11, 15:33:

DustyShinigami wrote on 2025-02-11, 15:13:

See, that was one of the things that confused me. I noticed that mentioned in another thread, but I don't seem to have any such file/driver. Nor did I see a command in the readme. I downloaded 3.09, which has Shsucdx.com and shcdx86.com. I don't believe I have DOSLFN. I take it that's an additional tool that allows longer file names? Thanks for the link to the documentation; I'll give it a look over. 😀

EDIT: Yeah, that was the same documentation I tried to decipher via the readme.

I think SHSUCDHD is from an older version then...? Judging from that linked documentation. That's 3.3, whereas I have 3.09. No such file is present.

The SHSUCDX 3.09 package contains only SHSUCDX.

There's a full package called SHSUCD 3-7 which includes everything including SHSUCDX 3.09. For loading images, this is the one you need.

Oh. So that's not the latest? I figured it was due to the date differences. 3.3 says 2005-2012 whereas 3.09 says 2006-2022. I'm wondering if 3.09 does it automatically...? I did download the one from GitHub initially, but that Master one was even more confusing. Too many files that don't look like I can do anything with in DOS. ^^;

That's the source code. It's no good for your purposes.

You want SHSUCD r3-7 from here: http://adoxa.altervista.org/shsucdx/

it has nothing to do with versions or release dates - what you're not understanding is that SHSUCDHD and SHSUCDX are totally different programs

SHSUCDX is a CDROM redirector for real (and virtual CDROM) drives just like MSCDEX

SHSUCDHD is a virtual physical layer driver for loading an image file as a emulated drive, and can be used without the use of SHSUCDX (by using MSCDEX instead)

megatron-uk wrote on 2025-02-11, 16:14:

That's the source code. It's no good for your purposes.

You want SHSUCD r3-7 from here: http://adoxa.altervista.org/shsucdx/

Ahhh, gotcha. I guess I thought that top one wasn't applicable for some reason and wound up picking 3.09. ^^; Thanks.

maxtherabbit wrote on 2025-02-11, 16:14:

it has nothing to do with versions or release dates - what you're not understanding is that SHSUCDHD are SHSUCDX totally different programs

SHSUCDX is a CDROM redirector for real (and virtual CDROM) drives just like MSCDEX

SHSUCDHD is a virtual physical layer driver for loading an image file as a emulated drive, and can be used without the use of SHSUCDX (by using MSCDEX instead)

I see. Thanks for clarifying.

LSS10999 wrote on 2025-02-11, 05:58:

I don't think SHSUCDX is the command for loading CD images. Shouldn't it be the ones other than SHSUCDX itself, such as SHSUCDHD […]
Show full quote

I don't think SHSUCDX is the command for loading CD images. Shouldn't it be the ones other than SHSUCDX itself, such as SHSUCDHD?

Here's the documentation for image handling tools (SHSUCDHD and some others).

I think what you want might be this, though I haven't really tried loading disk images myself as I haven't had such a need in DOS at the moment...
LH SHSUCDHD /F:"D:\CD IMAGES\SIMON_DOS\CD.ISO"

Though I think you might want to put your images in a path with short filenames and without whitespaces to avoid issues when loading the TSR. I wrapped your LFN path with double quotes but I'm not sure if it is the right way provided you have DOSLFN loaded.

I’m a bit lost at getting DOSLFN working, though I now have it on my system. I’ve not been able to add quotations when editing my batch files under DOS, so I’ve had to type words out followed by ‘^’ as I understand that’s the alternative…? So like “My Documents” becomes My^ Documents…?

I’ve added the initial command in my autoexec.bat file so SHSUCD is initialised when loading DOS, but I’m guessing that command you’ve shared is for the game’s batch file, right…?
I’ve tried adding it so it reflects my drive set up (physical F to E), but I’m still not having any luck getting it to mount/load. I’m guessing the directory of SHSUCDHD.EXE needs to be listed like I’ve put otherwise it won’t know where to look…?

Azarien wrote on 2025-02-11, 09:01:

I've never used shsucdhd but I believe it should be something like this:

LH SHSUCDHD /F:"D:\CD IMAGES\SIMON_DOS\CD.ISO"
LH SHSUCDX /D:SHSU-CDH

I’ve tried this too, in the batch file, but not having much luck. 😕 It tells me SHSUCDHD isn’t installed and that the file isn’t found under the directory for SHSU-CDH.

You've got spaces in your cd image filenames.

yes the caret is not a valid alternative, the image file needs to be specified at a valid 8.3 path

IIRC for a directory named "CD IMAGES" the resultant 8.3 path would be "CDIMAG~1"

maxtherabbit wrote on 2025-02-12, 14:53:

yes the caret is not a valid alternative, the image file needs to be specified at a valid 8.3 path

IIRC for a directory named "CD IMAGES" the resultant 8.3 path would be "CDIMAG~1"

Ahh, okay. If I got DOSLFN working, would that get around that issue? Or is it just something SHSUCD requires?

Still no luck so far. As a test, I’ve created a folder called ISO on the D drive, in there SIMON_DOS, and then copied the ISO. So it’s D:\ISO\SIMON_DOS\CD.ISO

In the autoexec.bat file, I’ve added:

LH C:\SHSUCD\SHSUCDX.COM /D:MSCD001, /L:E
LH C:\SHSUCD\SHSUCDHD.EXE

Both load up when DOS is initialised. Though I’m still having no luck at mounting the CD image in the custom batch file. So at the moment it’s:

LH C:\SHSUCD\SHSUCDHD.EXE /E:D:\ISO\SIMON_DOS\CD.ISO
LH C:\SHSUCD\SHSUCDX.COM /E:SHSU-CDH
D:\DOSGAMES\SIMON\SIMON.BAT

It’s still not finding the ISO though. 😕

EDIT: Changed ‘SIMON_DOS’ to ‘SIMONDOS’. Now have the batch file as:

LH C:\SHSUCD\SHSUCDHD /F:D:\ISO\SIMONDOS\CD.ISO

It says Unit 0 (warning: file size differs from volume size)

It says the SHSU-CDH CD image driver is installed. But having LH C:\SHSUCD\SHSUCDX /E:SHSU-CDH doesn’t appear to be doing anything. And it still doesn’t recognise an image being present.

DustyShinigami wrote on 2025-02-13, 00:08:

So it’s D:\ISO\SIMON_DOS\CD.ISO

'SIMON_DOS' is 9 characters which is more than what DOS could handle by default. Since you can see that folder name clearly then you must have DOSLFN loaded.

DOS can only handle up to 8 characters of file names and up to 3 characters of file extensions (hence 8.3 filenames).

Try putting the ISO in a path that complies with the 8.3 convention, and try again. You can simply rename SIMON_DOS to SIMONDOS.

Why are you using "/E" instead of "/D" ? Read the manual and use the parameters that it specifies instead of guessing...

LSS10999 wrote on 2025-02-13, 00:41:

'SIMON_DOS' is 9 characters which is more than what DOS could handle by default. Since you can see that folder name clearly then […]
Show full quote

DustyShinigami wrote on 2025-02-13, 00:08:

So it’s D:\ISO\SIMON_DOS\CD.ISO

'SIMON_DOS' is 9 characters which is more than what DOS could handle by default. Since you can see that folder name clearly then you must have DOSLFN loaded.

DOS can only handle up to 8 characters of file names and up to 3 characters of file extensions (hence 8.3 filenames).

Try putting the ISO in a path that complies with the 8.3 convention, and try again. You can simply rename SIMON_DOS to SIMONDOS.

I edited my initial post and changed it to SIMONDOS. But no, sadly I don’t have DOSLFN. I think when I went to that directory in DOS it was SIMON_~1 or something along those lines. I also asked earlier about how DOSLFN can be configured and someone informed me it only works with file managers that are designed for it.

jmarsh wrote on 2025-02-13, 00:43:

Why are you using "/E" instead of "/D" ? Read the manual and use the parameters that it specifies instead of guessing...

Because I figured that’s supposed to be the default CD drive letter, no? By default, everyone refers to it and types in ‘D’. My physical CD drive is F. I primarily use my emulated drive in Windows, which is E. And I usually set the physical drive in DOS to be E as well. It can’t be D as that’s my second HDD.