Very Computer

by **Jong-Min Pa** » Fri, 28 Feb 1997 04:00:00

I just got my first taste of Plug-and-Pray, and it's no fun.

Has anyone been able to run ctcm.exe under MSDOS 7.0 (part of Win95)?
I don't have early DOS by itself on the hard disk, and I still need to
boot linux from loadlin.exe. Currently I can't install linux until
I set the sb32pnp IDE as ide1 to access the cdrom drive.

Here are some problems I found:

1) When running ctcm.exe from DOS 7.0, it doesn't recognize ctpnp.cfg
in any directory (C:\, C:\CTCM) even if I set CTCM variable. It always
configures sb32pnp in a default way no matter how I change the ctpnp.cfg.

2) What is the purpose of ctcu.exe? It seems I can just edit ctpnp.cfg and
be done with it. Somehow ctcu complains that it can't run in a dos box,
even if I boot into DOS 7.0 of Win95. I had to run it from DOS 6 boot
disk, and it is VERY VERY SLOWWWWW. Each key response time is about
1.5 sec.

For now, I have to use a DOS 6 boot disk to run ctcm.exe and it is
working okay.

by **Markus Her** » Fri, 28 Feb 1997 04:00:00

> I just got my first taste of Plug-and-Pray, and it's no fun.

> Has anyone been able to run ctcm.exe under MSDOS 7.0 (part of Win95)?
> I don't have early DOS by itself on the hard disk, and I still need to
> boot linux from loadlin.exe. Currently I can't install linux until
> I set the sb32pnp IDE as ide1 to access the cdrom drive.

> Here are some problems I found:

> 1) When running ctcm.exe from DOS 7.0, it doesn't recognize ctpnp.cfg
> in any directory (C:\, C:\CTCM) even if I set CTCM variable. It always
> configures sb32pnp in a default way no matter how I change the ctpnp.cfg.

> 2) What is the purpose of ctcu.exe? It seems I can just edit ctpnp.cfg and
> be done with it. Somehow ctcu complains that it can't run in a dos box,
> even if I boot into DOS 7.0 of Win95. I had to run it from DOS 6 boot
> disk, and it is VERY VERY SLOWWWWW. Each key response time is about
> 1.5 sec.

> For now, I have to use a DOS 6 boot disk to run ctcm.exe and it is
> working okay.

Hi,
under DOS 7.0 leave your hands off ctcm.exe and ctcu.exe.
The appropriate programm you need is ctpnp.exe in your windows
directory.
Just execute this program from within win95 and the ctpnp.cfg file will
be updated with the right configuration.
Now you have to execute this ctpnp.exe everytime you want to initialize
your Blaster in plain DOS.

Hope this helps,
Markus
--
markus herb

--------------------------
phone : +49 7152 902971

by **Craig Galbrai** » Fri, 28 Feb 1997 04:00:00

>Hi,
>under DOS 7.0 leave your hands off ctcm.exe and ctcu.exe.
>The appropriate programm you need is ctpnp.exe in your windows
>directory.
>Just execute this program from within win95 and the ctpnp.cfg file will
>be updated with the right configuration.
>Now you have to execute this ctpnp.exe everytime you want to initialize
>your Blaster in plain DOS.

How do I load ctpnp.exe? I have a SB32 with rev 8 drivers and I don't see a
ctpnp.exe anywhere...just ctpnp.cfg and ctcm.exe.

Craig

http://www.geocities.com/Heartland/Plains/7997
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Craig Galbraith _____ _ _ _____

University of Prince Edward Island | _ | | | | | | |
Atlantic Veterinary College | | | | \ \/ / | |___
Class of 2000 |_| |_| \__/ |_____|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

by **Jong-Min Pa** » Sat, 01 Mar 1997 04:00:00

> > Has anyone been able to run ctcm.exe under MSDOS 7.0 (part of Win95)?
> > ...<snip>...
> > For now, I have to use a DOS 6 boot disk to run ctcm.exe and it is
> > working okay.
> under DOS 7.0 leave your hands off ctcm.exe and ctcu.exe.
> The appropriate programm you need is ctpnp.exe in your windows
> directory.

Thank you. Now, I can't seem to find ctpnp.exe anywhere. Is that part
of Win95 osr2? Can't find it in powertools, bug fixes, etc.

by **Erwin Maura** » Sat, 01 Mar 1997 04:00:00

> > > Has anyone been able to run ctcm.exe under MSDOS 7.0 (part of Win95)?
> > > ...<snip>...
> > > For now, I have to use a DOS 6 boot disk to run ctcm.exe and it is
> > > working okay.

> > under DOS 7.0 leave your hands off ctcm.exe and ctcu.exe.
> > The appropriate programm you need is ctpnp.exe in your windows
> > directory.

> Thank you. Now, I can't seem to find ctpnp.exe anywhere. Is that part
> of Win95 osr2? Can't find it in powertools, bug fixes, etc.

ctpnp.exe was around before the ctcm/ctcu programs. It was
Creative's early alternative to the Intel Plug&Play manager.
You can't find it anymore because it's obsolete and replaced
by perfectly working ctcm/ctcu.

Use ctcm in config.sys and ctcu in autoexec.bat if running
Dos6.2 and/or win3.1
Forget about ctcu and use ctcm in your autoexec.bat (not config.sys)
of the Dos Mode boot (or in dosstart.bat if booting to Dos
through another multiboot option).

Good luck,
Erwin

by **Jason Wagho** » Mon, 03 Mar 1997 04:00:00

----=_331a123a236438406c1e0c9.MFSBCHJLHS
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

On Fri, 28 Feb 1997 18:01:47 +0100, Erwin Maurau

>>> > under DOS 7.0 leave your hands off ctcm.exe and ctcu.exe.
>>> > The appropriate programm you need is ctpnp.exe in your windows
>>> > directory.

>>> Thank you. Now, I can't seem to find ctpnp.exe anywhere. Is that part
>>> of Win95 osr2? Can't find it in powertools, bug fixes, etc.

>>ctpnp.exe was around before the ctcm/ctcu programs. It was
>>Creative's early alternative to the Intel Plug&Play manager.
>>You can't find it anymore because it's obsolete and replaced
>>by perfectly working ctcm/ctcu.

>>Use ctcm in config.sys and ctcu in autoexec.bat if running
>>Dos6.2 and/or win3.1
>>Forget about ctcu and use ctcm in your autoexec.bat (not config.sys)
>>of the Dos Mode boot (or in dosstart.bat if booting to Dos
>>through another multiboot option).

So what's this then ? It came direct from my Windows directory. (For
the record, I have never installed any drivers earlier than rev 7 in
the current incarnation of my system)

CTPNP works, If you've got it use it, if not tough!

Jason
--
I think I'll be the first to start
To cherish, treasure & love as art
Every time one's cheeks do part
& The world is blessed with another fart

----=_331a123a236438406c1e0c9.MFSBCHJLHS
Content-Type: application/octet-stream
Content-Transfer-Encoding: base64
Content-Disposition: inline

<encoded_portion_removed>
bm1lbnQNCgD///8=

----=_331a123a236438406c1e0c9.MFSBCHJLHS--

by **Erwin Maura** » Wed, 05 Mar 1997 04:00:00

> On Fri, 28 Feb 1997 18:01:47 +0100, Erwin Maurau

> >>ctpnp.exe was around before the ctcm/ctcu programs. It was
> >>Creative's early alternative to the Intel Plug&Play manager.
> >>You can't find it anymore because it's obsolete and replaced
> >>by perfectly working ctcm/ctcu.

> >>Use ctcm in config.sys and ctcu in autoexec.bat if running
> >>Dos6.2 and/or win3.1
> >>Forget about ctcu and use ctcm in your autoexec.bat (not config.sys)
> >>of the Dos Mode boot (or in dosstart.bat if booting to Dos
> >>through another multiboot option).

> So what's this then ? It came direct from my Windows directory. (For

Well it just proves that you mailed me an unwanted binary file ...

I didn't argue that it didn't exist or that it doesn't work. It
does, but is replaced by ctcm.

Quote:> the record, I have never installed any drivers earlier than rev 7 in
> the current incarnation of my system)

fair enough, but did you assemble your computer or did someone else ?
I bet someone else did and installed (probably a good move at
the time) ctpnp.exe . I assembled my own (as I've been doing since
'89) and installed every card myself (tyan/network/adaptec/awe32/ati)
and win95 from the CD and I know for a fact that it is no part of
any windows. ctpnp.CFG is generated and in the windows directory,
I have it too, but ctpnp.EXE, noooo.

Quote:> CTPNP works, If you've got it use it, if not tough!

Well it obviously does, that was not the discussion, but things
move on and programs get updated. The new installations use the
upgrade called ctcm.

Quote:> Jason

Kind regards,
Erwin

by **Markus Her** » Wed, 05 Mar 1997 04:00:00

> > CTPNP works, If you've got it use it, if not tough!

> Well it obviously does, that was not the discussion, but things
> move on and programs get updated. The new installations use the
> upgrade called ctcm.

which refuses to work with some Mainboard Bios constellations.
CTCM just made my PC hang at bootup or shows the message that it don't
work in a Win 95 DOS-BOX when actually executed in plain DOS 7.0.
CTPNP.EXE just works fine for me. It doesn't help me to know to have an
'updated' program like CTCM, when it refuses to work in my system.
I'd rather use an 'oldfashioned' program, that works than a new one that
doesn't.
The original poster of this threat had problems with CTCM like me and i
just wanted to help.

To call my help 'a bunch of bunk' isn't very fair.
Only because you 'have never heard of this ctpnp.exe' it doesn't
mean that it doesn't exist even if you are a 'Tech Consultant' ;-))

--
markus herb

--------------------------
phone : +49 7152 902971

by **Erwin Maura** » Thu, 06 Mar 1997 04:00:00

> > > CTPNP works, If you've got it use it, if not tough!

> > Well it obviously does, that was not the discussion, but things
> > move on and programs get updated. The new installations use the
> > upgrade called ctcm.
> which refuses to work with some Mainboard Bios constellations.
> CTCM just made my PC hang at bootup or shows the message that it don't
> work in a Win 95 DOS-BOX when actually executed in plain DOS 7.0.

Well you probably don't want to try it anymore as you're obviously happy
with your current installation, but perhaps the following might help
other people :

I noticed that (for the plain DOS 7.0 mode) on one machine of mine
the line "devicehigh=d:\ctcm\ctcm.exe" in config.sys gives the message
you mention. When I changed the line to "device=d:\ctcm\ctcm.exe" it
worked, while on a more recent machine the opposite is true ...
I have it in my config.sys because I boot to DOS 7.0 using a short
cut with its specific autoexec and config. If you use dosstart.bat
the ctcm should be placed in there.

Quote:> CTPNP.EXE just works fine for me. It doesn't help me to know to have an
> 'updated' program like CTCM, when it refuses to work in my system.
> I'd rather use an 'oldfashioned' program, that works than a new one that
> doesn't.

Ah, but you switched to win95 didn't you ? No sorry, bad old joke, but
couldn't resist. I agree with you though, I would do the same.

Quote:> The original poster of this threat had problems with CTCM like me and i
> just wanted to help.

I don't remember holding against you ? As far as I'm concerned everyone
contributing and helping out is appreciated.

Kind regards,
Erwin

Very Computer

SoundBlaster 32 PNP ctcm.exe and DOS 7.0 (Win95 DOS)

SoundBlaster 32 PNP ctcm.exe and DOS 7.0 (Win95 DOS)

SoundBlaster 32 PNP ctcm.exe and DOS 7.0 (Win95 DOS)

SoundBlaster 32 PNP ctcm.exe and DOS 7.0 (Win95 DOS)

SoundBlaster 32 PNP ctcm.exe and DOS 7.0 (Win95 DOS)

SoundBlaster 32 PNP ctcm.exe and DOS 7.0 (Win95 DOS)

SoundBlaster 32 PNP ctcm.exe and DOS 7.0 (Win95 DOS)

SoundBlaster 32 PNP ctcm.exe and DOS 7.0 (Win95 DOS)

SoundBlaster 32 PNP ctcm.exe and DOS 7.0 (Win95 DOS)

SoundBlaster 32 PNP ctcm.exe and DOS 7.0 (Win95 DOS)