Reply 20 of 38, by kitten.may.cry
- Rank
- Member
Let me try that.
While I'm at it, why would MVSOUND.sys not get loaded, with all the drivers and device.sys edits?
Let me try that.
While I'm at it, why would MVSOUND.sys not get loaded, with all the drivers and device.sys edits?
kitten.may.cry wrote on 2020-06-12, 03:26:While I'm at it, why would MVSOUND.sys not get loaded, with all the drivers and device.sys edits?
I do not know. All I can think if that you might be loading it from an incorrect location? I have never tried FreeDOS so I'm not sure if that could be a conflict but I assume not.
Is a specific error displayed when you boot? You should see at least some sort of Media Vision text banner when the driver loads.
Oh, no, it definitely doesn't show anything like that.
MVSOUND.sys is in CONFIG.sys, aight...but not loaded at the same time.
Incorrect location, you say...what is the default location for MVSOUND.sys then, if not PAS directory?
kitten.may.cry wrote on 2020-06-12, 03:33:Oh, no, it definitely doesn't show anything like that.
MVSOUND.sys is in CONFIG.sys, aight...but not loaded at the same time.
Incorrect location, you say...what is the default location for MVSOUND.sys then, if not PAS directory?
Just looked again at the first image you posted. Indeed, it say that the MVSOUND.SYS is in the config.sys but not loaded. So, I assume you have the path correct.
So, no error is displayed when you reboot? What does the X parameter do when you add it at the end of the MVSOUND.SYS in your config.sys?
Nothing.
I get an error, when trying to load mscdex thing. (after I ran Install.exe in like, tenth time)
Packed file is corrupt.
kitten.may.cry wrote on 2020-06-12, 03:41:Nothing. […]
Nothing.
I get an error, when trying to load mscdex thing. (after I ran Install.exe in like, tenth time)
Packed file is corrupt.
OK. I have attached my MVSOUND.SYS (had to put it in a zip 'cos it doesn't allow to attach it otherwise). Unzip and put MVSOUND.SYS in the root of your C drive and modify your config.sys to be:
DEVICE=C:\MVSOUND.SYS B:388 D:5 Q:11 S1,220,1,5 M:0 J:0
Any other line in config.sys and autoexec.bat, comment it out by putting "rem" in front of it. E.g:
rem c:\pastudio\mscdex.exe /d:mvcd001 /m:10 /v
ROOT OF MY C DRIVE...okay.
That string you keep referring to, is simply replaced with whatever INSTALL.exe got in there.
Testing it.
Didn't load.
kitten.may.cry wrote on 2020-06-12, 03:54:That string you keep referring to, is simply replaced with whatever INSTALL.exe got in there.
Yeah, better stop running install.exe, it will keep replacing things. You want to manually edit the config.sys and autoexec.bat instead.
Once you made a change, reboot and run the CUSDIAG program.
Back to rem c:\pastudio\mscdex.exe /d:mvcd001 /m:10 /v
Gives me an error.
Packed file is corrupt.
Also, copying mvsound.sys in the root & changing config.sys didn't do anything.
You know what's funny?
PAS.exe wouldnt run, if I didn't have MVSOUND.sys loaded.
It'd imply I didn't have it loaded.
kitten.may.cry wrote on 2020-06-12, 04:03:Back to rem c:\pastudio\mscdex.exe /d:mvcd001 /m:10 /v
Gives me an error.
Packed file is corrupt.
OK. Back to basics. Backup your existing config.sys and autoexec.bat by renaming them:
ren config.sys config.bak
ren autoexec.bat autoexec.bak
Now create a new config.sys file that just loads the MVSOUND.SYS from the C root.
Reboot. Run CUSDIAG.
I think, I just screwed up my DOS...by renaming autoexec.bat.
Need a minute to fix that.
It didn't change anything, however...my PASTUDIO folder is corrupted.
In particular, CUSDIAG...so I had to patch into your PAS16 folder to get to CUSDIAG.
I could do a fresh FreeDOS installation at this point...
You got Discord?
I'm just tired and I'd like to continue at the later hour, with a fresh copy of FreeDOS, of course.
Here is the archived mediavision help page for your card:
http://web.archive.org/web/19961110151224/htt … ort/tpastud.htm
cyclone3d wrote on 2020-06-12, 05:19:Here is the archived mediavision help page for your card:
http://web.archive.org/web/19961110151224/htt … ort/tpastud.htm
Oh, that's big!
SYSTEM.ini...it has to be WIN95 or 98 then...not FreeDOS.
I get it...
BLOODY HELL! NO MORE FreeDOS from now on!
MS-DOS 6.22 IS A FREAKING MIRACLE.
Everything is working now.
Huge thanks to cyclone3d, who indirectly hinted at my OS not being up to par.
Also, pan069 for sticking around for so long.
kitten.may.cry wrote on 2020-06-12, 17:55:Huge thanks to cyclone3d, who indirectly hinted at my OS not being up to par.
Also, pan069 for sticking around for so long.
You're welcome.
I wasn't even thinking that FreeDOS could have been the problem.
Glad you got it working.
Someone oughta add this to PAS FAQ: do not use FreeDOS 😁
kitten.may.cry wrote on 2020-06-12, 18:38:Someone oughta add this to PAS FAQ: do not use FreeDOS 😁
FreeDOS is great but it does have a few corner case issues . You have found one . I was lucky enough to experience a different one with the FreeDOS version of FDISK . If dev is still active on this project, maybe such issues should be reported upstream .