I think my msvcrt.dll file got overwritten by some older version and I'm getting the same problem I used to have before I got a newer version of msvcrt.dll.
I remember somebody on PlanetZ gave me the new version but I don't think I can find it on the forums anymore.
Can someone post a link or something? I'm getting constant crashes.. sheesh!
By the way, people were right, the ProPack works great.
the old msvcrt.dll problem
http://infinitevortex.com/demos/msvcrt.zip
Use at your own risk, I have no idea what this file may do to your system, I run Win98SE on this system right now.
Use at your own risk, I have no idea what this file may do to your system, I run Win98SE on this system right now.
-
The Z Station
- Posts: 294
- Joined: Mon Apr 15, 2002 4:00 pm
- Location: Seattle, WA
- Contact:
Mr. Sub, tried that file but the existing one I have is more recent.....
3DAT/Pulsar was running awesomely well for the last 5 days then these popped up again - msvcrt & base faults... The thing is, these errors only appear on Win98SE, not on WinXP Pro.... Also, I never had these problems before I totally clean re-installed Win98SE.
One thing I found is that the 29160 SCSI and Pulsar2+ are sharing IRQ 3. I don't know why they seem to stick together. I have 2 IRQ's open but both seem to like the same spot. Not sure if this make for an unstable environment for Pulsar? I'll have to re-position those 2 and hopefully get them assigned on different IRQ. But, yet again, Pulsar 3.01 runs very smoothly on XP Pro???!!!! So..... the quest continues...
I downloaded the Libraries update from Microsoft last night... We'll see....
3DAT/Pulsar was running awesomely well for the last 5 days then these popped up again - msvcrt & base faults... The thing is, these errors only appear on Win98SE, not on WinXP Pro.... Also, I never had these problems before I totally clean re-installed Win98SE.
One thing I found is that the 29160 SCSI and Pulsar2+ are sharing IRQ 3. I don't know why they seem to stick together. I have 2 IRQ's open but both seem to like the same spot. Not sure if this make for an unstable environment for Pulsar? I'll have to re-position those 2 and hopefully get them assigned on different IRQ. But, yet again, Pulsar 3.01 runs very smoothly on XP Pro???!!!! So..... the quest continues...
I downloaded the Libraries update from Microsoft last night... We'll see....
Yes sharing IRQs can cause problems (I believe this is mentioned quite a few times around here). That file I posted was taken from a rock solid Win98SE system with Pulsar 2.04a. Use at your own risk (backup your file first), but sounds like your version got overwritten with a version that is giving you problems.
-
The Z Station
- Posts: 294
- Joined: Mon Apr 15, 2002 4:00 pm
- Location: Seattle, WA
- Contact:
When I checked and compared those 2 files, I kept what I had.
With regards to IRQ sharing, I kinda ruled that out on account that Pulsar 3.01 is humming on the XP Pro. As mentioned earlier, these error only happens on 98SE AND, it never happened before until I clean istalled from the same 98SE CD.....
However, (thinking to myself) When I had the SB Live! MP3+ 5.1, that seem to have kept the SCSI and Pulsar2 on different IRQs.
Seems like 3DAT/Pulsar3.01 was running better on my last config:
Asus CUBX v1.005
PIII-700MHz
512MB PC100
Adaptec 29160
ATI Rage Fury Maxx 64MB (2 resources)
SB Live! MP3+ 5.1 (2 resources)
Win98SE + NetBEUI via parallel
tripleDATII
Pulsar2+
SERIAL PORTS = 1 ENABLED in BIOS
PARALLEL PORT = ENABLED in BIOS
USB = DISABLED in BIOS
versus...
Asus CUBX v1.007 (possibility problematic new BIOS?)
Same Proc
Same RAM
Same SCSI controller
ATI Xpert 2000
D-Link 530+TX NIC (disabled in Win98SE)
Pulsar2+
tripleDATII
SERIAL PORTS = BOTH DISABLED in BIOS
PARALLEL PORT = DISABLED in BIOS
USB = ENABLED (disabled in Win98SE)
All I have on 98SE is tripleDAT 3.06/3.11b, and Pulsar 3.01 - no XTC. As simple as this setup maybe, you would think that you won't encounter any problems at all....
So, I don't have any problem of having another program write over the msvcrt.dll file at all since all I have are the Creamware programs....
The search continues.....
With regards to IRQ sharing, I kinda ruled that out on account that Pulsar 3.01 is humming on the XP Pro. As mentioned earlier, these error only happens on 98SE AND, it never happened before until I clean istalled from the same 98SE CD.....
However, (thinking to myself) When I had the SB Live! MP3+ 5.1, that seem to have kept the SCSI and Pulsar2 on different IRQs.
Seems like 3DAT/Pulsar3.01 was running better on my last config:
Asus CUBX v1.005
PIII-700MHz
512MB PC100
Adaptec 29160
ATI Rage Fury Maxx 64MB (2 resources)
SB Live! MP3+ 5.1 (2 resources)
Win98SE + NetBEUI via parallel
tripleDATII
Pulsar2+
SERIAL PORTS = 1 ENABLED in BIOS
PARALLEL PORT = ENABLED in BIOS
USB = DISABLED in BIOS
versus...
Asus CUBX v1.007 (possibility problematic new BIOS?)
Same Proc
Same RAM
Same SCSI controller
ATI Xpert 2000
D-Link 530+TX NIC (disabled in Win98SE)
Pulsar2+
tripleDATII
SERIAL PORTS = BOTH DISABLED in BIOS
PARALLEL PORT = DISABLED in BIOS
USB = ENABLED (disabled in Win98SE)
All I have on 98SE is tripleDAT 3.06/3.11b, and Pulsar 3.01 - no XTC. As simple as this setup maybe, you would think that you won't encounter any problems at all....
So, I don't have any problem of having another program write over the msvcrt.dll file at all since all I have are the Creamware programs....
The search continues.....
Hi Z-Station & Subhuman
I have identical problem on my new ASUS TUSL2-C mobo !
Sometimes when I load a project (only with Pulsar Mixer in) "loader" CRASH !!!
<I>PULSAR spowodowa³ b³¹d: nieprawid³owa strona w
module <FONT COLOR="CCCC22">MSVCRT.DLL przy 016f:7800d17d.</FONT>
Rejestry:
EAX=00770008 CS=016f EIP=7800d17d EFLGS=00210202
EBX=00000000 SS=0177 ESP=0065d7d8 EBP=0065d7f4
ECX=00000000 DS=0177 ESI=0366db8c FS=227f
EDX=00000007 ES=0177 EDI=00000001 GS=0000</I>
My setup:
ASUS TUSL2-C (bios rev.1011)
PIII 1000 Mhz (not overclkd)
256 MB (1xPC 133)
Pulsar 2 (IRQ 9 not shared)
Win98 SE (fresh install)
Pulsar 3.01b (fresh install)
THE END - zero other cards & USB, every standard tweaks done, etc. ...... ?!?!?
p.s.
Under XP Pro everything is great
<font size=-1>[ This Message was edited by: darolek on 2002-04-25 17:15 ]</font>
I have identical problem on my new ASUS TUSL2-C mobo !
Sometimes when I load a project (only with Pulsar Mixer in) "loader" CRASH !!!
<I>PULSAR spowodowa³ b³¹d: nieprawid³owa strona w
module <FONT COLOR="CCCC22">MSVCRT.DLL przy 016f:7800d17d.</FONT>
Rejestry:
EAX=00770008 CS=016f EIP=7800d17d EFLGS=00210202
EBX=00000000 SS=0177 ESP=0065d7d8 EBP=0065d7f4
ECX=00000000 DS=0177 ESI=0366db8c FS=227f
EDX=00000007 ES=0177 EDI=00000001 GS=0000</I>
My setup:
ASUS TUSL2-C (bios rev.1011)
PIII 1000 Mhz (not overclkd)
256 MB (1xPC 133)
Pulsar 2 (IRQ 9 not shared)
Win98 SE (fresh install)
Pulsar 3.01b (fresh install)
THE END - zero other cards & USB, every standard tweaks done, etc. ...... ?!?!?
p.s.
Under XP Pro everything is great
<font size=-1>[ This Message was edited by: darolek on 2002-04-25 17:15 ]</font>