So what exactly is the difference to the normal version when called with the /T switch?

/T switch?

I feel I'm learning something new 😀

What does the switch do?

Kahenraz wrote:

Both CTCM and CTCU use a very mundane check to guess whether it's running in windows. It looks for the environment variable "winbootdir". How clever.

Say, is that the same check used by Creative's installer for the DOS drivers? (It is pretty much the only program I've ever seen that absolutely insists on being run from MS-DOS 6.22 and not DOS 7.x, but I've never understood what sort of check it uses.)

What does the switch do?

I just tried it. It says it's for some kind of Windows 95 testing mode. I'm assuming it removes the Windows checks for CTCM.. I think. However, this switch does not exist for CTCU; so my patch is still relevant for this. 😀

Say, is that the same check used by Creative's installer for the DOS drivers?

The installer checks against the DOS version. I did try but I wasn't able to find this check by dropping it into a hex editor. It will have to be run through a debugger to find the location to be patched.

It is pretty much the only program I've ever seen that absolutely insists on being run from MS-DOS 6.22 and not DOS 7.x

The SETVER trick works for this. No need for 6.22.

Kahenraz wrote:

The SETVER trick works for this. No need for 6.22.

Are you sure about that? Someone has previously mentioned trying SETVER with no success. Perhaps we are talking about different things?
Getting my AWE64 working in pure DOS mode

It works fine. Changes to SETVER won't take effect until the system it rebooted; maybe that was the problem. Also, SETVER has to be run at least once to initialize in memory after the reboot.

It's most likely that the user in the other thread made a mistake.

Yes I have also used SETVER successfully!

Mau1wurf1977, I was following your guide while attempting to change the IRQ, MIDI, and DMA values of my PNP SB AWE 64 GOLD and I was unable to get them to "stick" no matter what combination I used. This is despite successfully passing all tests in CTCU.

With CTCU I can only change the values in any "configuration" other than 0. The problem was that CTCM *always* resets the PNP bios back to configuration 0 which has the values I don't want. CTCM has to be run after every reboot and this changes the values in CTPNP.CFG back to configuration 0. 😒

I found that using CTCM with the "/T" switch will always load CTCM with the configuration in CTPNP.CFG instead of having the card decide and then update CTPNP.CFG with the values I don't want.

To summarize: always use CTCM with the "/T" switch.. ?

Have you experienced anything like this?

I set ctpnp.cfg READ ONLY, so ctcm can not write to the file.
Previously I set the desired values in ctpnp.cfg.

Then you can check if ctcm sets the same resources as given in ctpnp.cfg by checking the BLASTER setting after a call. If it is different you have to free up some resource you would like to have.
f.e. check if it reserved in BIOS for ISA, PnP OS is set to YES and so on.

I didn't test to that extent as I am now back to DOS 6.22 again. Might look into it again when I have some time 😀 But I keep the /T switch in mind!