It's been a REALLY long time since I've had to do any installs -
Acronis True Image has spoiled me. I use some DOS programs but
just file managers etc.
So this is probably going to be fairly pathetic to most of you.
I'm trying to set up a 166MHz P1 for a DOS/95 game box. The
machine works fine, even though it's from Sept. 97.
I have looked at various websites, read seemingly relevant parts
of MS-DOS books and program help files, and I have made some
progress but I don't think I'm going to make any more.
The machine has 96MB of RAM, a SB AWE64 card, a Matrox graphics
card, an MS mouse serial mouse. (I finally managed to get the
mouse to work in DOS. Sigh.)
I put command.com in the root dir as well as having it in the 95
windows\command. I'd like to just have one, but whatever I do,
nothing works the way it should.
Everything works fine in 95B but I want to work in DOS mostly. I
have a 2GHz 98SELite machine for "current" things.
Problems:
1.
There is great utility called ALIAS and I just can NOT get it to
run from autoexec.bat. I can run it from its own little batch
file but I'd rather not. It's been driving me NUTS for years - I
used to run it just fine from autoexec.bat 15 years ago. WHAT
happened, I don't know. And now I REALLY need it.
2.
There is no sound in DOS. I remember getting the message "cannot
initialize device" when I tried to run AWEUTIL, I believe.
3.
Possibly lots of others but this is as far as I've gotten. Any
looking-ahead advice will be appreciated.
My boot files are as follows:
config.sys:
device=c:\sys\himem.sys
dos=high,umb
device=c:\sys\emm386.exe noems
lastdrive=G
DEVICEHIGH=C:\PROGRA~1\CREATIVE\CTSND\DRV\CTSB16.SYS /UNIT=0
/WIN95 /BLASTER=A:220 I:10 D:3 H:5
DEVICEHIGH=C:\PROGRA~1\CREATIVE\CTSND\DRV\CTMMSYS.SYS
autoexec.bat:
@echo off
prompt $p$g
SET COMPSPEC=C:\COMMAND.COM
PATH=c:\sys;c:sys\QM
SET SOUND=C:\PROGRA~1\CREATIVE\CTSND
SET MIDI=SYNTH:1 MAP:E MODE:0
SET BLASTER=A220 I10 D3 H5 P300 E620 T6
rem C:\WINDOWS\COMMAND\MSCDEX.EXE /D:MSCD000 /M:6
C:\SYS\ALIAS\ALIAS.COM /F c:\sys\alias\myalias.txt
LH doskey.com
LH mouse.com
cls
The paths are OK. The weird (?) stuff in the boot files was done
because of what I read in one place or another /should/ be done.
I'm trying a variety of DOS menu programs although XTree is
always a great file manager, so that's why the QM entry (I don't
know if PATH=C:\sys includes all the subdirectories so I added
QM just in case). I will try more menus, but I'd like the thing
to work first.
Is there a kind soul that could please help me? Thanks.
t.
--
"May you live in interesting times."
(curse, origin disputed)
> So this is probably going to be fairly pathetic to most of you.
*** Not at all.
> I'm trying to set up a 166MHz P1 for a DOS/95 game box. The
> machine works fine, even though it's from Sept. 97.
*** It will run DOS just fine.
> I have looked at various websites, read seemingly relevant parts
> of MS-DOS books and program help files, and I have made some
> progress but I don't think I'm going to make any more.
*** For a good list of DOS publications, see:
http://www.chebucto.ca/~ak621/DOS/DOS-Pub.html
> The machine has 96MB of RAM, a SB AWE64 card, a Matrox graphics
> card, an MS mouse serial mouse. (I finally managed to get the
> mouse to work in DOS. Sigh.)
*** Try CuteMouse. I run a serial trackball and CuteMouse works very
well. Plus, it uses far less memory than the Microsoft driver.
> I put command.com in the root dir as well as having it in the 95
> windows\command. I'd like to just have one, but whatever I do,
> nothing works the way it should.
> Everything works fine in 95B but I want to work in DOS mostly.
*** Dump WIN 95. It is a disaster when it comes to running DOS cames,
especially where sound is required. Keep your Pentium I as strictly a DOS
machine.
> Problems:
> 1.
> There is great utility called ALIAS and I just can NOT get it to
> run from autoexec.bat. I can run it from its own little batch
> file but I'd rather not. It's been driving me NUTS for years - I
> used to run it just fine from autoexec.bat 15 years ago. WHAT
> happened, I don't know. And now I REALLY need it.
*** Simply call that batch file from AUTOEXEC.bat. Perhaps something
needs to be loaded first which that batch files does.
> 2.
> There is no sound in DOS. I remember getting the message "cannot
> initialize device" when I tried to run AWEUTIL, I believe.
*** You need to load a correct SoundBlaster driver, and with the proper
settings. A typical AUTOEXEC.bat line is:
BLASTER=A220 I7 D0 T4
I see you have multiple BLASTER and sound settings, so there may be
some confusion there. Try remarking out all sound-related lines and
running the Sound Blaster install package, if you have it. A good book is
"The Ultimate Sound Blaster Book". It's listed in the "DOS Publications"
URL I gave earlier.
> My boot files are as follows:
> config.sys:
> device=c:\sys\himem.sys
> dos=high,umb
> device=c:\sys\emm386.exe noems
*** Some games require Expanded Memory. Enable EMS.
> lastdrive=G
*** Reduce this to the actual last drive letter being used in your
system.
> DEVICEHIGH=C:\PROGRA~1\CREATIVE\CTSND\DRV\CTSB16.SYS /UNIT=0
> /WIN95 /BLASTER=A:220 I:10 D:3 H:5
> DEVICEHIGH=C:\PROGRA~1\CREATIVE\CTSND\DRV\CTMMSYS.SYS
> autoexec.bat:
> @echo off
> prompt $p$g
> SET COMPSPEC=C:\COMMAND.COM
> PATH=c:\sys;c:sys\QM
> SET SOUND=C:\PROGRA~1\CREATIVE\CTSND
> SET MIDI=SYNTH:1 MAP:E MODE:0
> SET BLASTER=A220 I10 D3 H5 P300 E620 T6
> rem C:\WINDOWS\COMMAND\MSCDEX.EXE /D:MSCD000 /M:6
> C:\SYS\ALIAS\ALIAS.COM /F c:\sys\alias\myalias.txt
> LH doskey.com
> LH mouse.com
> cls
> The paths are OK. The weird (?) stuff in the boot files was done
> because of what I read in one place or another /should/ be done.
*** Some of that advice may be conflicting, but I can't comment without
knowing what your needs are.
> I'm trying a variety of DOS menu programs although XTree is
> always a great file manager, so that's why the QM entry (I don't
> know if PATH=C:\sys includes all the subdirectories so I added
> QM just in case). I will try more menus, but I'd like the thing
> to work first.
*** You should have DOS and probably BATCH in there as well. You may
want to try Graphic Vision or Sword for more power.
> Is there a kind soul that could please help me? Thanks.
> t.
*** I am kind. (-:
One or more links to websites
for the referred program(s)
can be found at:
http://www.chebucto.ca/~ak621/DOS/Websites.html
Richard Bonner
http://www.chebucto.ca/~ak621/DOS/
<SNIP>
Thanks for the first reply to my post. I will save it and when I
have several (hopefully - although you may be the ONLY kind
person out there) I will try different things. I will also look
into the links you provided.
While I understand your suggestion of dumping 95, there are
quite a few things that require 95 that I am interested in - but
I think should be able to accommodate both without too much
trouble once I sort out the conflicts. I do have the original
discs etc so will try again.
The annoying thing is, I /think/ it all used to work fine ages
ago when I didn't need it!
Thanks again.
>There is great utility called ALIAS and I just can NOT get it to
>run from autoexec.bat
What error does it generate?
>2.
>There is no sound in DOS. I remember getting the message "cannot
>initialize device" when I tried to run AWEUTIL, I believe.
If you want it to run dos then get a bog standard SB16 card and dos drivers
for it. Perhaps the AWE64 card doesn't have dos drivers.
>device=c:\sys\emm386.exe noems
I agree with Richard, enable EMS.
device=c:\sys\emm386.exe RAM AUTO
>PATH=c:\sys;c:sys\QM
make c:sys\QM = c:\sys\QM
> On 05 Dec 2008 07:53:15 GMT, thanatoid
> <wai...@the.exit.invalid> wrote:
>
>>There is great utility called ALIAS and I just can NOT get
>>it to run from autoexec.bat
>
> What error does it generate?
When I press one of the F-keys (it's a shortcut utility, F keys
instead of typing 10 command lines, written before F11 and F12
appeared on keyboards) it either does nothing or types a single
letter. But that's a lesser problem. I can always go back to
a.bat, a one line batch file I had to run it before I needed it
ALL the time. It's /one/ letter, what the hell.
>>2.
>>There is no sound in DOS. I remember getting the message
>>"cannot initialize device" when I tried to run AWEUTIL, I
>>believe.
>
> If you want it to run dos then get a bog standard SB16 card
> and dos drivers for it. Perhaps the AWE64 card doesn't
> have dos drivers.
Yes, it does, even has a DOS "utility" program, which told me
"unable to initialize device".
It never gave me problems, but I was also smarter 10 years ago
than I am now.
>>device=c:\sys\emm386.exe noems
>
> I agree with Richard, enable EMS.
OK.
> device=c:\sys\emm386.exe RAM AUTO
>
>>PATH=c:\sys;c:sys\QM
>
> make c:sys\QM = c:\sys\QM
Now that last line I do /not/ understand.
Thanks for your advice.
> foxidrive <got...@woohoo.invalid> wrote in
> news:cs4jj4pevhsdj0dig...@4ax.com:
>
>> On 05 Dec 2008 07:53:15 GMT, thanatoid
>> <wai...@the.exit.invalid> wrote:
>>
>>> There is great utility called ALIAS and I just can NOT get
>>> it to run from autoexec.bat
>>
>> What error does it generate?
>
> When I press one of the F-keys (it's a shortcut utility, F keys
> instead of typing 10 command lines, written before F11 and F12
> appeared on keyboards) it either does nothing or types a single
> letter. But that's a lesser problem. I can always go back to
> a.bat, a one line batch file I had to run it before I needed it
> ALL the time. It's /one/ letter, what the hell.
I'd suggest that doskey and Alias (I've not heard of this utilty) are
conflicting; or maybe Alias doesn't work under w95?. Try remming out the
doskey line.
>
>>> 2.
>>> There is no sound in DOS. I remember getting the message
>>> "cannot initialize device" when I tried to run AWEUTIL, I
>>> believe.
>>
>> If you want it to run dos then get a bog standard SB16 card
>> and dos drivers for it. Perhaps the AWE64 card doesn't
>> have dos drivers.
>
> Yes, it does, even has a DOS "utility" program, which told me
> "unable to initialize device".
> It never gave me problems, but I was also smarter 10 years ago
> than I am now.
I'm stumped there.
>
>>> device=c:\sys\emm386.exe noems
>>
>> I agree with Richard, enable EMS.
>
> OK.
>
>> device=c:\sys\emm386.exe RAM AUTO
>>
>>> PATH=c:\sys;c:sys\QM
>>
>> make c:sys\QM = c:\sys\QM
>
> Now that last line I do /not/ understand.
The way it is at present it's a relative path. you need to add the
backslash between the colon and the "sys\QM"
>
> Thanks for your advice.
>
>
--
"Nuns ! NUNS ! REVERSE ! REVERSE !"
> ak...@chebucto.ns.ca (Richard Bonner) wrote:
> <SNIP>
> Thanks for the first reply to my post. I will save it and when I
> have several (hopefully - although you may be the ONLY kind
> person out there) I will try different things. I will also look
> into the links you provided.
*** There are many kind people here that will provide good advice.
> While I understand your suggestion of dumping 95, there are
> quite a few things that require 95 that I am interested in - but
> I think should be able to accommodate both without too much
> trouble once I sort out the conflicts. I do have the original
> discs etc so will try again.
*** OK. I can help with some of those conflicts, but be aware that some
games may never work properly or completely.
> The annoying thing is, I /think/ it all used to work fine ages
> ago when I didn't need it!
*** It may have. I am not saying that no DOS games will work under WIN
95, only that it can be a major hassle to iron out some of the problems
trying to provide the environment they need without interference from
Windows. WIN 95 was the real start of my hate for Windows and Microsoft,
in general, eventually leading to my complete abandonment of that system.
> Thanks again.
> t.
*** You're welcome.
Richard Bonner
http://www.chebucto.ca/~ak621/DOS/
> > foxidrive <got...@woohoo.invalid> wrote:
> >
> >> On 05 Dec 2008 07:53:15 GMT, thanatoid
> >> <wai...@the.exit.invalid> wrote:
> >>
> >>> There is great utility called ALIAS and I just can NOT get
> >>> it to run from autoexec.bat
> >>
> >> What error does it generate?
> >
> > When I press one of the F-keys (it's a shortcut utility, F keys
> > instead of typing 10 command lines, written before F11 and F12
> > appeared on keyboards) it either does nothing or types a single
> > letter. But that's a lesser problem. I can always go back to
> > a.bat, a one line batch file I had to run it before I needed it
> > ALL the time. It's /one/ letter, what the hell.
> I'd suggest that doskey and Alias (I've not heard of this utilty) are
> conflicting; or maybe Alias doesn't work under w95?. Try remming out the
> doskey line.
*** Good advice. I was not thinking about ALIAS being a DOSKEY-style of
utility.
> >>> 2.
> >>> There is no sound in DOS. I remember getting the message
> >>> "cannot initialize device" when I tried to run AWEUTIL, I
> >>> believe.
> >>
> >> If you want it to run dos then get a bog standard SB16 card
> >> and dos drivers for it. Perhaps the AWE64 card doesn't
> >> have dos drivers.
> >
> > Yes, it does, even has a DOS "utility" program, which told me
> > "unable to initialize device".
> > It never gave me problems, but I was also smarter 10 years ago
> > than I am now.
> I'm stumped there.
*** Windows (especially WIN 95) is well known to generate conflicts when
it comes to DOS audio.
thanatoid: Try booting into DOS 7 only and see if things operate as
they should. Once we solve any problems there, you can try to run the
whole works under Windows. As I recall, the problem lies in telling
Windows to provide certain things or to not provide them. There is a
series of checkboxes somewhere that do this.
I am going into work for a short time this morning and have notes
there from a decade ago. I will review them and post here again.
> >>> PATH=c:\sys;c:sys\QM
> >>
> >> make c:sys\QM = c:\sys\QM
> >
> > Now that last line I do /not/ understand.
> The way it is at present it's a relative path. you need to add the
> backslash between the colon and the "sys\QM"
*** That is correct. The backslash is required as a precursor to
subdirectories.
Richard Bonner
http://www.chebucto.ca/~ak621/DOS/
> On Sat, 06 Dec 2008 03:24:55 -0000, thanatoid
> <wai...@the.exit.invalid> wrote:
<SNIP>
>>>> There is great utility called ALIAS and I just can NOT
>>>> get it to run from autoexec.bat
>>>
>>> What error does it generate?
>>
>> When I press one of the F-keys (it's a shortcut utility, F
>> keys instead of typing 10 command lines, written before
>> F11 and F12 appeared on keyboards) it either does nothing
>> or types a single letter. But that's a lesser problem. I
>> can always go back to a.bat, a one line batch file I had
>> to run it before I needed it ALL the time. It's /one/
>> letter, what the hell.
>
> I'd suggest that doskey and Alias (I've not heard of this
> utilty) are conflicting; or maybe Alias doesn't work under
> w95?. Try remming out the doskey line.
ALIAS is for DOS only, but I believe it will work in a DOS
window although it's really not needed under windows, and there
are Win utils that do exactly the same thing. Alias is one of
those great old free PCMags utils.
I don't believe it conflicts with doskey although it has a
similar and more advanced function built in. But I'll try
remming it out. I only put doskey in because alias didn't work,
IIRC.
>>>> 2.
>>>> There is no sound in DOS. I remember getting the message
>>>> "cannot initialize device" when I tried to run AWEUTIL,
>>>> I believe.
>>>
>>> If you want it to run dos then get a bog standard SB16
>>> card and dos drivers for it. Perhaps the AWE64 card
>>> doesn't have dos drivers.
>>
>> Yes, it does, even has a DOS "utility" program, which told
>> me "unable to initialize device".
>> It never gave me problems, but I was also smarter 10 years
>> ago than I am now.
>
> I'm stumped there.
Likewise. And I checked all the IRQ etc settings and they are
the same when I run the "SET" command and in both config and
autoexec. 'Tis the season to be jolly I guess.
>>> device=c:\sys\emm386.exe RAM AUTO
I'll do that - I never heard of "auto" but it sounds like you
know what you're talking about.
Unfortunately the only DOS book I have is for ver 5 and they
made some changes afterwards.
>>>> PATH=c:\sys;c:sys\QM
>>>
>>> make c:sys\QM = c:\sys\QM
>>
>> Now that last line I do /not/ understand.
>
> The way it is at present it's a relative path. you need to
> add the backslash between the colon and the "sys\QM"
Oh, that was just a typo which I never noticed. There ARE
backslashes where they should be.
Thanks for your advice.
t.
>> >>> 2.
>> >>> There is no sound in DOS. I remember getting the
>> >>> message "cannot initialize device" when I tried to run
>> >>> AWEUTIL, I believe.
>> >>
>> >> If you want it to run dos then get a bog standard SB16
>> >> card and dos drivers for it. Perhaps the AWE64 card
>> >> doesn't have dos drivers.
>> >
>> > Yes, it does, even has a DOS "utility" program, which
>> > told me "unable to initialize device".
>> > It never gave me problems, but I was also smarter 10
>> > years ago than I am now.
>
>> I'm stumped there.
>
> *** Windows (especially WIN 95) is well known to generate
> conflicts when it comes to DOS audio.
>
> thanatoid: Try booting into DOS 7
I took out the "start GUI" command in msdos.sys so it stays in
DOS7 until I type win.
> only and see if things
> operate as they should.
As I mentioned in the post of a moment ago, I checked all the
IRQ's and everything matches but no go.
> Once we solve any problems there, you can try
> to run the whole works under Windows. As I recall, the
> problem lies in telling Windows to provide certain things
> or to not provide them. There is a series of checkboxes
> somewhere that do this.
Well, the sound DOES work under Windows, it just doesn't work
under DOS. Sigh.
> I am going into work for a short time this morning and
> have notes
> there from a decade ago. I will review them and post here
> again.
Thank you /very/ much for taking so much time to help me.
I am not moving as fast - IOW have done almost nothing since you
originally replied - as I should be on this problem, because my
/OTHER/ (this) computer (on which I depend for the net among
other things) has started "misbehaving" as well. My life saver
of 5+ years, Acronis True Image, refuses to restore an image.
Are you at all familiar with it? It reboots (as it should), says
"loading Acronis loader" (or something), and then instead of a
nice few screens which I go through and 10 minutes later have a
perfect machine, the caps lock and scroll lock lights blink and
nothing happens until I press the power button. I have done this
at least 20 times now, fixed the MBR (IF it needed fixing),
reinstalled Acronis twice, changed the system date (I once had a
program go insane in a PARTICULAR MONTH of a PARTICULAR year -
needless to say, I don't use it any more), and I have gone back
to an older registry. Nothing doing. I am worried. Weird things
are happening (BIG surprise) and it is time to go back to a good
image. Never had this problem in 5+ years and I use Acronis a
lot since I have /never/ managed to learn to "leave well enough
alone".
Thanks again.
> thanatoid (wai...@the.exit.invalid) wrote:
>
>> ak...@chebucto.ns.ca (Richard Bonner) wrote:
>> <SNIP>
>
>> Thanks for the first reply to my post. I will save it and
>> when I have several (hopefully - although you may be the
>> ONLY kind person out there) I will try different things. I
>> will also look into the links you provided.
>
> *** There are many kind people here that will provide
> good advice.
Well, it's a nice change from some other "help groups" which
seem to have been degenerating in a most unpleasant manner.
>> While I understand your suggestion of dumping 95, there
>> are quite a few things that require 95 that I am
>> interested in - but I think should be able to accommodate
>> both without too much trouble once I sort out the
>> conflicts. I do have the original discs etc so will try
>> again.
>
> *** OK. I can help with some of those conflicts, but be
> aware that some games may never work properly or
> completely.
I realize that, I am going one step at a time. For now, all I
want is for the sound to start working in DOS. I ran the same
game in Windows and it HAD sound. Infuriating. But I know there
are SOME games that /only/ run from DOS so that's why I want
this taken care of first. (The old little 95 games run fine,
too.)
>> The annoying thing is, I /think/ it all used to work fine
>> ages ago when I didn't need it!
>
> *** It may have. I am not saying that no DOS games will
> work under WIN 95, only that it can be a major hassle to
> iron out some of the problems trying to provide the
> environment they need without interference from Windows.
I know exactly what you mean, the weird thing, it ODES work
under Windows, just WILL NOT work under DOS, and I just admit
that even though I use XTree all the time, I have never done
much serious/extensive work in DOS.
> WIN 95 was the real start of my hate for Windows and
> Microsoft, in general, eventually leading to my complete
> abandonment of that system.
I understand completely. After tweaking 95B for about 5 years I
got it to where it worked like it should have out of the box,
but 98SE is as far as I've ever gone with MS OS's. Someday it
WILL be Linux time.
Thanks again.
>I know exactly what you mean, the weird thing, it ODES work
>under Windows, just WILL NOT work under DOS
You can load DosBox under Windows and run all your dos games full screen
with sound. It's free... http://www.dosbox.com/
There are other dos emulations around too.
Will it work with 95? Never mind, I'll just check the site.
Thanks for a brilliant suggestion. I have heard of the dosbox
just like of the Linux "win boxes" but never knew much about
them. Sounds promising.
*** For a super DOSKEY, try Toddy.
> ak...@chebucto.ns.ca (Richard Bonner) wrote:
> > Try booting into DOS 7...
> I took out the "start GUI" command in msdos.sys so it stays in
> DOS7 until I type win.
> > ...see if things operate as they should.
> As I mentioned in the post of a moment ago, I checked all the
> IRQ's and everything matches but no go.
*** When in DOS only, run the game's setup to see if it will recognise
the sound card. I can't remember: Are you sure the sound card will run in
DOS? If it's a Windoze-only card, forget it.
> > Once we solve any problems there, you can try
> > to run the whole works under Windows. As I recall, the
> > problem lies in telling Windows to provide certain things
> > or to not provide them. There is a series of checkboxes
> > somewhere that do this.
> Well, the sound DOES work under Windows, it just doesn't work
> under DOS. Sigh.
*** Well, once I get a chance to review my notes, you may be able to run
the game through Windows and have the sound.
> > I am going into work for a short time this morning and
> > have notes there from a decade ago. I will review them and post
> > here again.
> Thank you /very/ much for taking so much time to help me.
*** You're welcome.
> I am not moving as fast - IOW have done almost nothing since you
> originally replied - as I should be on this problem, because my
> /OTHER/ (this) computer (on which I depend for the net among
> other things) has started "misbehaving" as well. My life saver
> of 5+ years, Acronis True Image, refuses to restore an image.
> Are you at all familiar with it?
*** No. I don't use Windows anymore. Sorry.
Richard Bonner
http://www.chebucto.ca/~ak621/DOS/
> > thanatoid (wai...@the.exit.invalid) wrote:
> >> While I understand your suggestion of dumping 95, there
> >> are quite a few things that require 95 that I am
> >> interested in - but I think should be able to accommodate
> >> both without too much trouble once I sort out the
> >> conflicts. I do have the original discs etc so will try
> >> again.
> >
> > *** OK. I can help with some of those conflicts, but be
> > aware that some games may never work properly or
> > completely.
> I realize that, I am going one step at a time. For now, all I
> want is for the sound to start working in DOS. I ran the same
> game in Windows and it HAD sound. Infuriating.
*** That was my experience with Windows. I upgraded to DOS in 1999 and
my health is much better now. (-:
> > *** I am not saying that no DOS games will
> > work under WIN 95, only that it can be a major hassle to
> > iron out some of the problems trying to provide the
> > environment they need without interference from Windows.
> I know exactly what you mean, the weird thing, it ODES work
> under Windows, just WILL NOT work under DOS,
*** Perhaps the sound card is Windows-only. Do other games run
with sound in DOS?
> and I just admit
> that even though I use XTree all the time, I have never done
> much serious/extensive work in DOS.
*** I used to use GUI shells but now shun because they require too
much extra work to get anything done. I find an automated command line to
be far superior.
> > WIN 95 was the real start of my hate for Windows and
> > Microsoft, in general, eventually leading to my complete
> > abandonment of that system.
> I understand completely. After tweaking 95B for about 5 years I
> got it to where it worked like it should have out of the box,
> but 98SE is as far as I've ever gone with MS OS's. Someday it
> WILL be Linux time.
*** I have several versions of Linux, but rarely run them because I am
able to do all my work in DOS.
Richard
> thanatoid (wai...@the.exit.invalid) wrote:
<SNIP>
>> My life saver of 5+ years, Acronis
>> True Image, refuses to restore an image. Are you at all
>> familiar with it?
>
> *** No. I don't use Windows anymore. Sorry.
I forgot, sorry - you said so already!
Anyway, BION, after several days of 1000% perplexity and
suicidal thoughts, a possible solution occurred to me PLUS I
found an Acronis TECH CHAT link where the technician confirmed
that I identified the problem. So everything is OK and I feel a
lot less stupid since I figured it out myself! I am now ready to
tackle this damn DOS sound thing full-force! :-# (gritting
teeth)
> http://www.chebucto.ca/~ak621/DOS/
You know, I have a feeling that could be a very interesting
site, but I have been trying for 2 days and NO CONNECTION. ???
> On 06 Dec 2008 18:44:39 GMT, thanatoid
> <wai...@the.exit.invalid> wrote:
>
>>I know exactly what you mean, the weird thing, it ODES work
>>under Windows, just WILL NOT work under DOS
>
> You can load DosBox under Windows and run all your dos
> games full screen with sound. It's free...
> http://www.dosbox.com/
I checked t out - it seems it would be perfect for my 2GHz
machine, but I want to run it on a 166MHz with 96MB of RAM and
it /sounds/ like it won't work at all (or very badly) on
something like that.
> There are other dos emulations around too.
I may check into them. For now, my attitude is basically, I will
get DOS sound or I will die trying. GRRR!
(I just solved a horrible problem with my 2GHz computer so I
feel "empowered", if you excuse the term.)
> > thanatoid (wai...@the.exit.invalid) wrote:
> <SNIP>
> >> My life saver of 5+ years, Acronis
> >> True Image, refuses to restore an image. Are you at all
> >> familiar with it?
> >
> > *** No. I don't use Windows anymore. Sorry.
> I forgot, sorry - you said so already!
*** No problem.
> Anyway, BION, after several days of 1000% perplexity and
> suicidal thoughts, a possible solution occurred to me PLUS I
> found an Acronis TECH CHAT link where the technician confirmed
> that I identified the problem. So everything is OK and I feel a
> lot less stupid since I figured it out myself!
*** Tackling things one's self is a good way to learn. I am completely
self-taught regarding computers. All those DOS books and magazines I
mentioned in an earlier posts really did work. (-:
http://www.chebucto.ca/~ak621/DOS/DOS-Pub.html
> I am now ready to tackle this damn DOS sound thing full-force! :-#
> (gritting teeth)
*** I found my reference. Go into "Program Properties" and fill in the
appropriate information there. Then go down into "Advanced..." and try
some of the options there. Be sure to only change *one* thing at a time to
see what happens. As a precaution, write down all the defaults before
making any changes at all.
> > http://www.chebucto.ca/~ak621/DOS/
> You know, I have a feeling that could be a very interesting
> site, but I have been trying for 2 days and NO CONNECTION. ???
*** I checked and it seems fine. What is the error your get? Try this
direct link to the main page:
http://www.chebucto.ca/~ak621/DOS/DOS-Head.html
Richard Bonner
http://www.chebucto.ca/~ak621/DOS/
> > On 06 Dec 2008 18:44:39 GMT, thanatoid
> > <wai...@the.exit.invalid> wrote:
> > You can load DosBox under Windows and run all your dos
> > games full screen with sound. It's free...
> > http://www.dosbox.com/
> I checked it out - it seems it would be perfect for my 2GHz
> machine, but I want to run it on a 166MHz with 96MB of RAM and
> it /sounds/ like it won't work at all (or very badly) on
> something like that.
> > There are other dos emulations around too.
> I may check into them. For now, my attitude is basically, I will
> get DOS sound or I will die trying. GRRR!
*** If it's a DOS-compatible sound card, your game should eventually
produce sound. If not, you will have to run it under Windows.
Richard Bonner
http://www.chebucto.ca/~ak621/DOS/
to OP:
it looks like you are using the wrong drivers for your soundcard. the
presence of "CTSB16.SYS" suggests that you are using SBBASIC.EXE
drivers.
you need two packages:
CTCM*.EXE - pnp configurator
S64BASIC.EXE - awe64 drivers
they can be found here:
http://www.mpoli.fi/files/hardware/SOUND/CLABS/index.html
> thanatoid (wai...@the.exit.invalid) wrote:
<SNIP>
> *** Tackling things one's self is a good way to learn. I
> am completely self-taught regarding computers. All those
> DOS books and magazines I mentioned in an earlier posts
> really did work. (-:
>
> http://www.chebucto.ca/~ak621/DOS/DOS-Pub.html
>
The "computer guy" guy where I used to work in the 90's had PC
Magazine from whenever it started just about. Twice a year or so
he'd bring in a sizable stack and leave it lying around - no one
would touch it, so it'd end up in the dumpster. That's when
computers were computers! I grabbed a few issues but wish I had
ALL of them now!
>> I am now ready to tackle this damn DOS sound thing
>> full-force! :-# (gritting teeth)
>
> *** I found my reference. Go into "Program Properties"
> and fill in the appropriate information there. Then go down
> into "Advanced..." and try some of the options there. Be
> sure to only change *one* thing at a time to see what
> happens. As a precaution, write down all the defaults
> before making any changes at all.
Excellent. Thanks.
>> > http://www.chebucto.ca/~ak621/DOS/
>
>> You know, I have a feeling that could be a very
>> interesting site, but I have been trying for 2 days and NO
>> CONNECTION. ???
>
> *** I checked and it seems fine. What is the error your
> get? Try this direct link to the main page:
>
> http://www.chebucto.ca/~ak621/DOS/DOS-Head.html
>
> Richard Bonner
> http://www.chebucto.ca/~ak621/DOS/
The browser says "connecting", and then it times out and says
"Failed - could not connect to "www.chebucto.ca". Just tried it
again. Tried the main domain too, same thing. Strange.
I use 2 browsers, Opera and OffByOne. I usually only run into
this with VERY old links - understandably, since they are no
longer valid - but sometimes the main domain will be there, even
if blank.
> >> > http://www.chebucto.ca/~ak621/DOS/
> >
> >> You know, I have a feeling that could be a very
> >> interesting site, but I have been trying for 2 days and NO
> >> CONNECTION. ???
> >
> > *** I checked and it seems fine. What is the error your
> > get?
> >
> > Richard Bonner
> The browser says "connecting", and then it times out and says
> "Failed - could not connect to "www.chebucto.ca". Just tried it
> again. Tried the main domain too, same thing. Strange.
*** It may be that your ISP has Chebucto blocked for some reason. Send
an e-mail to them and ask. While waiting for an answer, try connecting
just to chebucto:
http://www.chebucto.ca
Also, try a friend's system that uses a different ISP.
Richard Bonner
http://www.chebucto.ca/~ak621/DOS/
<SNIP>
> *** It may be that your ISP has Chebucto blocked for some
> reason. Send an e-mail to them and ask.
[Extended laughter break.]
> While waiting for
> an answer, try connecting just to chebucto:
> http://www.chebucto.ca
I already did, see prev. post. Same thing.
> Also, try a friend's system that uses a different ISP.
>
> Richard Bonner
> http://www.chebucto.ca/~ak621/DOS/
If you knew where I live and had any idea of what's going on
with my ISP, you'd realize what a nice chuckle I had over your
suggestions. I am still astonished whenever I actually get on
the net!
Boy, I miss living in Vancouver! Civilization can be so nice,
Gordon Campbell notwithstanding!
BTW, AFA the "sound in DOS" problem, I DID manage to have the
damn machine "say" something to me in DOS, but it failed the
MIDI test. So there /is/ progress being made, albeit snail-
paced.
> BTW, AFA the "sound in DOS" problem, I DID manage to have the
> damn machine "say" something to me in DOS, but it failed the
> MIDI test. So there /is/ progress being made, albeit snail-
> paced.
>
in case you missed my earlier post:
you need two packages:
CTCM*.EXE - pnp configurator
S64BASIC.EXE - awe64 drivers
they can be found here:
http://www.mpoli.fi/files/hardware/SOUND/CLABS/index.html
"ctsb16.sys" is for sb16 cards. run the ctcm utilities to set the card
to use the available IRQ. then install awe64 drivers.
> [Extended laughter break.]
> If you knew where I live and had any idea of what's going on
> with my ISP, you'd realize what a nice chuckle I had over your
> suggestions. I am still astonished whenever I actually get on
> the net!
*** OK, so where are you and who is your ISP?
> Boy, I miss living in Vancouver! Civilization can be so nice,
> Gordon Campbell notwithstanding!
*** I am at the opposite end in Nova Scotia. Come live here. (-:
> BTW, AFA the "sound in DOS" problem, I DID manage to have the
> damn machine "say" something to me in DOS, but it failed the
> MIDI test. So there /is/ progress being made, albeit snail-
> paced.
*** Try the driver package mentioned in a previous post. Otherwise use
the soundblaster set-up program. If you don't have it, e-mail me and I
will send it to you.
Richard Bonner
http://www.chebucto.ca/~ak621/DOS/
<SNIP>
> *** OK, so where are you and who is your ISP?
In the interest of maintaining the illusion of anonymity on the
net, that question is never answered. ;-)
>> Boy, I miss living in Vancouver! Civilization can be so
>> nice, Gordon Campbell notwithstanding!
>
> *** I am at the opposite end in Nova Scotia. Come live
> here. (-:
It's very pretty there, I know, but a little cold and windy,
Frankly, after living in several of the larger Canadian cities I
have decided the /only/ acceptable climate is the south-west BC.
I've never been to the island (lived there for 11 years and
never made it - I hate traveling) but I imagine it is equally
nice.
>> BTW, AFA the "sound in DOS" problem, I DID manage to have
>> the damn machine "say" something to me in DOS, but it
>> failed the MIDI test. So there /is/ progress being made,
>> albeit snail- paced.
>
> *** Try the driver package mentioned in a previous post.
> Otherwise use the soundblaster set-up program. If you don't
> have it, e-mail me and I will send it to you.
I am kind of enjoying the struggle. So thanks, but let me see
what I can do first.
I have downloaded about 15 Creative etc. programs etc. It is
amazing what some will do that others don't. Not to mention
their rather bizarre file formats.
Yesterday after changing a few things, I passed ALL tests -
albeit in a DOS Box under Win 95. IIRC, I did NOT get the final
test passed last time, also under Windows. I thought I'd enjoy
my (hopefully not illusory) success and wait until later today
to conduct the same test in pure DOS.
[I was slightly concerned about the extremely low volume until I
realized I must have the plug in the line out - and I did. Would
it KILL THEM to paint the tiny letters next to the jacks black?
As you may recall, the old SB cards had a small power amp chip
quite sufficient to drive a pair of desktop speakers. So volume
is fine now.]
Then I'm going to install a DOS mixer and make a multi-menu - or
modify the one I had a few days ago. Then I'm going to mess
around with refresh rates - I would /like to run at 80 or higher
but from the one page or so that I've read it seems a lot of the
old games only run at 60. That could be a drag on the old eyes.
Still can't connect to your domain. What's the numerical IP
address?
Cheers.
> ak...@chebucto.ns.ca (Richard Bonner) wrote:
> > *** OK, so where are you and who is your ISP?
> In the interest of maintaining the illusion of anonymity on the
> net, that question is never answered. ;-)
*** Understood.
> >> Boy, I miss living in Vancouver! Civilization can be so
> >> nice, Gordon Campbell notwithstanding!
> >
> > *** I am at the opposite end in Nova Scotia. Come live
> > here. (-:
> It's very pretty there, I know, but a little cold and windy,
*** It can be, but was warm and windy here yesterday. Parts of the
Maritimes hit 16 degrees with lots of rain.
> > *** Try the driver package mentioned in a previous post.
> > Otherwise use the soundblaster set-up program. If you don't
> > have it, e-mail me and I will send it to you.
> I am kind of enjoying the struggle. So thanks, but let me see
> what I can do first.
*** That struggle will teach you more about DOS and its relationship
with Windows.
(Snip)
> Yesterday after changing a few things, I passed ALL tests -
> albeit in a DOS Box under Win 95. IIRC, I did NOT get the final
> test passed last time, also under Windows. I thought I'd enjoy
> my (hopefully not illusory) success and wait until later today
> to conduct the same test in pure DOS.
*** Again, look into "Properties".
> Then I'm going to install a DOS mixer and make a multi-menu - or
> modify the one I had a few days ago. Then I'm going to mess
> around with refresh rates - I would /like to run at 80 or higher
> but from the one page or so that I've read it seems a lot of the
> old games only run at 60. That could be a drag on the old eyes.
*** Not around fluorescent lights - they refresh at 60 cps. Opposing
rates on a monitor can cause eye strain and headaches.
I actually allow my refresh to float so that it picks the best rate
depending on what's on the screen. Sometimes it's as low as 60 and
other times as high as 80. Since I use incandescent lights around my
computers for the most part, it's not a problem to have something other
than 60.
> Still can't connect to your domain. What's the numerical IP
> address?
*** I don't have that handy. I will post it here when I get back to
work.
Richard Bonner
http://www.chebucto.ca/~ak621/DOS/
Remember me mentioning how I could NOT get alias to work?
Sigh....
I feel pretty stupid - I left out one of the /alias/ things in
the path in the line in autoexec.bat... Now, of course, it works
just fine... PLUS I finally (heck, it's only been 16 years) read
the whole help file - it's even more flexible and useful than I
thought... Actually MS doskey isn't so bad either...
"Funny" (/kinda/ funny) how I never noticed my error for so
long. Getting old...
> *** For a super DOSKEY, try Toddy.
> http://www.chebucto.ca/~ak621/DOS/Websites.html
For some reason, I /was/ just able to connect and I am looking
forward to exploring your site!
(BTW, I just glanced at it for a moment before writing this, and
I feel compelled to tell you I have NEVER had the guts to go on
a roller coaster!)
Also, good news - after about a month, I have DOS sound working
perfectly.
I had to do it the brutal way - I spent weeks with about 20
different Creative Blaster driver files and utilities, with
/some/ advances made but no full success. Finally I said, ****
**, and I wiped the drive and put DOS 6.21 on it. (Then I used a
partition manager to make the rest of the 8.4 GB drive usable.)
It may be that once you have Win95 installed it takes a magician
to make the DOS sound work, but whatever. It's done. I /may/
install Win 3.11 since there a few games that require it. The
funny thing is I'm not even into games, but it was something to
do, and it has been interesting.
I certainly appreciate you sticking by me and offering all the
good advice.
Regards
t.
--
"We don't see things as they are, we see things as we are."
Anais Nin
> http://www.chebucto.ca/~ak621/DOS/
I can NOT believe how comprehensive your DOS websites page is...
Amazing...
And seeing as you seem an organized and capable person, I have a
feeling VERY few if any are defunct...
Looking forward to exploring... There is definitely that
/something/ about the DOS screen that just *disappeared* with
9x, you know?
> I feel pretty stupid - I left out one of the /alias/ things in
> the path in the line in autoexec.bat... Now, of course, it works
> just fine... PLUS I finally (heck, it's only been 16 years) read
> the whole help file - it's even more flexible and useful than I
> thought...
*** That is one of the entries on my "DOS Tips" page. People who buy a
program for one purpose and have it for a while, often forget, or usually
never realised in the first place, that it can do more. As such, they go
out and buy another program when it is not always necessary.
> > *** For a super DOSKEY, try Toddy.
> > http://www.chebucto.ca/~ak621/DOS/Websites.html
> For some reason, I /was/ just able to connect and I am looking
> forward to exploring your site!
*** Nice to know Chebucto is accessible to you. They host a great number
of interesting information sites. I can't remember the URL to access them
though. Try searching on "Chebucto" "Neighbourhood". Note the spelling of
the latter. (-:
> (BTW, I just glanced at it for a moment before writing this, and
> I feel compelled to tell you I have NEVER had the guts to go on
> a roller coaster!)
*** I love them, but in recent years am more interested in amusement
park and ride history:
http://www.CEC.chebucto.org/ClosPark/
This summer, try the kiddie coasters and work up.
> Also, good news - after about a month, I have DOS sound working
> perfectly.
*** Excellent.
> I had to do it the brutal way - I spent weeks with about 20
> different Creative Blaster driver files and utilities, with
> /some/ advances made but no full success. Finally I said, ****
> **, and I wiped the drive and put DOS 6.21 on it. (Then I used a
> partition manager to make the rest of the 8.4 GB drive usable.)
*** That would do it. I found Windoze to be constantly interfering with
my DOS work and eventually dumped it.
> It may be that once you have Win95 installed it takes a magician
> to make the DOS sound work, but whatever. It's done.
*** Not necessarily. The "Properties" sections are the key to getting
DOS games to run under Win 9.x. Even so, sound is the most troublesome.
> I /may/
> install Win 3.11 since there a few games that require it. The
> funny thing is I'm not even into games, but it was something to
> do, and it has been interesting.
*** At least with Win 3.x, one can turn it off. (-:
> I certainly appreciate you sticking by me and offering all the
> good advice.
>
> t.
*** Not a problem.
Richard Bonner
http://www.chebucto.ca/~ak621/DOS/
> ak...@chebucto.ns.ca (Richard Bonner) wrote:
> > http://www.chebucto.ca/~ak621/DOS/
> I can NOT believe how comprehensive your DOS websites page is...
> Amazing...
*** Thanks, I appreciate that. I tried to put subjects on it that were
less well covered on other DOS websites.
As for the "Links" page, I do a lot of research on my own, but must
also credit the many regulars in this and other groups that suggest
programs and websites.
> And seeing as you seem an organized and capable person, I have a
> feeling VERY few if any are defunct...
*** If that is the case, I am lucky. With four websites to care for (two
of them very large), I don't often get to check for broken links very
often. Fortunately when I do find one, I can easily make fast corrections
because, using Chebucto's shell server, I can do correction work right on
line with no uploading required. It's very fast.
Further regarding links, I have used the W3C's "Link Checker" but it
chokes on pages with more than a certain number of links. )-: As a
result, I must check links manually. In some ways, I prefer this because I
don't like their program's output format.
> Looking forward to exploring...
*** Enjoy. Feel free to e-mail with comments, suggestions or questions.
> There is definitely that /something/ about the DOS screen that just
> *disappeared* with 9x, you know?
*** Windoze DOS or command line screens are so bland, and are
often relegated to some little box in one corner of the screen. Mine is
dressed up with colour and layout. I have gotten comments from people that
are unfamiliar with full-blown DOS screens - chiefly regarding the
coloured text.
Richard Bonner
http://www.chebucto.ca/~ak621/DOS/
> thanatoid (wai...@the.exit.invalid) wrote:
<SNIP>
>> And seeing as you seem an organized and capable person, I
>> have a feeling VERY few if any are defunct...
>
> *** If that is the case, I am lucky. With four websites
> to care for (two of them very large), I don't often get to
> check for broken links very often. Fortunately when I do
> find one, I can easily make fast corrections because, using
> Chebucto's shell server, I can do correction work right on
> line with no uploading required. It's very fast.
Well, I tried a few, and there were one or two that led nowhere
or to a VERY different page (I'm sorry, I did not note the
URL's). But that is only to be expected, as the sound of sheep
bleating "VISTA!!! VISTA!!!" is drowning out even the sound of
jet engines above...
> Further regarding links, I have used the W3C's "Link
> Checker" but it
> chokes on pages with more than a certain number of links.
> )-:
> As a result, I must check links manually.
I was just going to suggest one of those auto-checkers - I've
never used one. There are quite a few around that I've seen
mentioned in web site building/managing sections of (mostly
British) magazines from a few years ago. Maybe try a different
one? You have SO many links it must take HOURS and HOURS to
check them manually!
> In some
> ways, I prefer this because I don't like their program's
> output format.
I agree, manual is usually better as a rule. Still, some things
are nice to automate. I needed to do something 173 times a few
days ago and I used MacroMagic and it was just delightful
watching it do its thing, and saving me from a certain mental
collapse...
>> Looking forward to exploring...
>
> *** Enjoy. Feel free to e-mail with comments, suggestions
> or questions.
>
>> There is definitely that /something/ about the DOS screen
>> that just *disappeared* with 9x, you know?
>
> *** Windoze DOS or command line screens are so bland, and
> are often relegated to some little box in one corner of the
> screen. Mine is dressed up with colour and layout. I have
> gotten comments from people that are unfamiliar with
> full-blown DOS screens - chiefly regarding the coloured
> text.
I am constantly astounded by almost never seeing anything but
the default windows colors and all the icons in vertical rows on
the left... In my early days I used to go nuts with the Windows
colors, which always elicited astonishment from co-workers (now
I just have everything in shades of gray :-) . I also used to
set some REALLY crazy colors in XTGold, but I'm too old for that
now.
And my Win9x taskbar is vertical on the left and my icons are
grouped in various areas of the screen depending on type of app.
This also seems very rare. WHAT is it with people?
(Sorry to talk about Windows, but it was slightly relevant to
your statement.)
Regards,
t.