base.dll error with fresh V3 Install--?

JD · Post by JD » Wed Feb 13, 2002 9:17 am

after running pulsar for 8 hrs i went to add an insert in one of my synth channels. that was the start of the problem-blue screen of death. i rebooted, launched pulsar and tried to load my project--that was the first base.dll error. i then tried to rebuild my project from scartch. but then on save and exit, base.dll error.
it had been a while so i just decided to format and reinstall windows and pulsar. now with a fresh install ofwin98 and only pulsar v3 i can't even load the pulsar mixer, before it finishes it gives me a base.dll error and pulsar crashes to windows. no other cards are being used, just the agp graphics and pulsar I and II on irq 10. even installing 3.01 gives the same error. trying to load pulsar mixer gives a base.dll error and crashes pulsar everythime.

i'm not sure what to do. perhaps flash the bios again. or put 2.01 back on the machine first and then install 3.0. i thought 3.0 was a complete install with no other version needing to be present.
any tips or ideas much appreciated
JD

Win 98 SE 4.10.2222.A
P800
Cusl-2
815 chipset utility installed
360 Ram
Pular I and II on irq 10

bassdude · Post by **bassdude** » Wed Feb 13, 2002 1:13 pm

Vers 3.0 is a complete install.
I've run into trouble before where a fresh install of windows hasn't worked properly and then have had to do another re-install again before it would work.
This is one of the reasons I bought Norton Ghost, so when I did get a working install complete with drivers and audio tweaks I wouldn't have to keep going through the pain-in-the-arse windows install and pulsar install.
You could try re-installing pulsar over itself again to see if that works?

bassdude · Post by **bassdude** » Wed Feb 13, 2002 1:15 pm

PS
Are you following the recommended order when installing the 815 installation utilty?
i.e.
1. Install windows
2. Install 815 utility
3. Install video drivers
4. everything else

JD · Post by JD » Thu Feb 14, 2002 7:57 am

yeah i did follow the instructions of doing the 815 utility first. then i did the pulsar drivers and then the pulsar software. i let windows provide the driver for the graphics card. i don't think that would be the problem, but i'll downloaded the lastest graphic drivers, install them, and the install pulsar and see what happens.

Rene · Post by **Rene** » Thu Feb 14, 2002 8:30 am

Which version of those Intel 815 utility are you using??
I had problems with the newest version 3.20 and therefore I switched back to 2.80...

...maybe that helps!!

JD · Post by JD » Thu Feb 14, 2002 9:59 am

i had an old ghost copy from 3.0 w/o 3.1. i reloaded that to my c: partition and guess what happened at pulsar boot up. base.dll error. couldn't even load project default. tried to reinstall pulsar software on top and keep getting errors that a file is corrupt or bad media. i have several downloads of all the files in different folders and all are producing this same error. going to remove the cards, reload windows, and then reinstall cards, drivers, and hopefully the software.
should pulsar I be on top of pulsar II card in pci slot or visa versa?

Neutron · Post by **Neutron** » Thu Feb 14, 2002 12:23 pm

try opening your computer and re seating the boards in the pci slot.

Spirit · Post by **Spirit** » Thu Feb 14, 2002 6:26 pm

I had a very similar problem: continual crash on exit in base.dll. It would happen maybe 75% of the time. I couldn't pin down exactly what it was so I basically did everything:

got a new copy of the base.dll
cleaned registry
deleted flakey programs
upgraded from Win98 to Win98SE
set a static swap file
optimised
defragged
reinstalled

Now it happens about 10% of the time, most often when I had the program open for many hours.

Why ? Who knows, I've tried everything (except wiggling the card). Now I'll try that too. Interesting at least to know that I'm not alone in the Universe.

This problem never happened with version 2.04 so I'm hopeful it will go away again with version 3.1.

But then I'm an optimist

JD · Post by JD » Tue Feb 19, 2002 6:35 pm

well, 99 installs later and the same thing, base.dll error. i tried ME, 98 with all updates, ect ect. followed all the tips on the web. i'm at a lose. today i decided to give up and us the big mixer and then lightwave synth gave me the same base.dll error. reboot, load puslar and started building a project, and then out of curioustiy i erased the big mixer and to my suprise the pulsar mixer loaded. but to be honest, i think when i go back to the project i'll get the same error, however i won't know till friday.
after a full week of computer re-installs i'm about to convert to external synths only. never had problems with my wave xt, novation or roland gear like this. perhaps someday all the quirks will be ironed out, if i'm still alive i'll be able to enjoy it.

subhuman · Post by **subhuman** » Wed Feb 20, 2002 8:48 am

Suggestion: avoid all the old mixers, they don't work that well in Version 3. Use only the new mixers in Version 3.

Finally - are you using a 98Lite? I think someone had this problem who used the 'drastic' (or whatever its called) setting.

JD · Post by JD » Wed Feb 20, 2002 9:36 am

yeah i am using 98 lite, but only to remove itmes i dont' use. help files, screen savers, ect. i use only the 98 shell with launch bar b/c i've read that the 95 shell can cause problems. i did do a fresh 98 install without 98lite but had the same error. is the xp environment stable enough that it would be worth my while to give it a try?

JD

Post by **garyb** » Wed Feb 20, 2002 9:46 am

your problem is NOT which os you use if you've used 98.you have a problem in your install somewhere.i have been running for a long time with no troubles in 98 and you can too.be patient, it'll work well,eventually. obviously,SOMETHING has changed,check the bios and all the optimizations,carefully.(as if you weren't)

[ This Message was edited by: garyb on 2002-02-20 09:50 ]

subhuman · Post by **subhuman** » Wed Feb 20, 2002 10:05 am

it's definitely not your OS - I too have had rock solid 98SE installs with V3.01. Make sure you have all drivers installed, install Pulsar V3.01 update after you install everything else, check your DirectX version/installation...

Spirit · Post by **Spirit** » Wed Feb 20, 2002 5:25 pm

I too get occasional base.dll crashes (on exit only). I'm running Direct X 8. Is this good, bad or indifferent ?

cheers

bassdude · Post by **bassdude** » Wed Feb 20, 2002 5:52 pm

On the DAW I've kept the version of directx to 6.1

I'd read that directx 8 for DAWs is bad although I don't know how true this is.

JD · Post by JD » Wed Feb 20, 2002 10:30 pm

i don't know much about how RAM works in the sense of programming, but could cheap, generic RAM cause this problem? i do all my hard disk recording on a mac with DP3 and use pulsar for synths and adat routing so i thought i could get away with generic ram, but perhaps not. i'm waiting on some crucial memory due in friday. if it helps i'll post so.

ps
i've also upgrade to dx8.1 but i think i search the web for an earlier version and try that.

[ This Message was edited by: JD on 2002-02-20 22:31 ]

Spirit · Post by **Spirit** » Thu Feb 21, 2002 1:05 am

Hi JD,
Seems suspicious to me that we have such similar systems and the same base.dll problem. Let's keep swapping info.

The Z Station · Post by **The Z Station** » Wed Apr 17, 2002 1:25 pm

Salut!

Finally, after searching through google.com, I found this forum! Thank heavens that I'm not the only one getting this error! I've posted a thread in CW's Forum but haven't had a response - yet...

[SYNOPSIS]
After a clean Win98SE install and with ONLY Creamware stuff (Pulsar 3.01, tripleDAT 3.06 & 3.11b, DAT4WIN) with DirectX 8.1, I was getting an Illegal Operations Page Fault on the MSVCRT.DLL & BASE.DLL files right on during the boot process or when I start tripleDAT 3.11b! I haven't even begun to start to use Win98SE and bam! After a reboot, it works fine! This only happens when I first turn the computer on after a few hours of having the computer turned off. This does NOT happen on Pulsar 3.xx loaded on the WinXP Pro - peculiar.... So, the culprit may lie elsewhere.

I've been running tripleDAT 3.xx + Pulsar 3.0x for 7 months now and it has been working very well. I recently clean installed Win98SE with VERY MINIMAL componets (no network agents, monitors, multimedia, etc.). I only have DirectX 8.1 loaded in. Perhaps, this could be the culprit having read any reference in this post. I'll try going down to DX7 (not Yamaha) and see if this will eliminate this dreaded Illegal Operations Page Fault on BASE.DLL. Although, WinXP comes with DX8.1.... But, it's not Win98SE. Do you think that DirectX behaves differently on each OS? As for the MSVCRT.DLL, that still remains a mystery. Still doing some testing...

[TECH SPEC]
MoBo: Asus CUBX BIOS v1.007
Proc: PIII 700MHz
RAM: 512MB PC100
Video: ATI Xpert 2000 (driver requires DX8.1)
ISA: tripleBOARD II
PCI5: Pulsar II Plus (bottom)
PCI4: Adaptec 29610 SCSI controller
PCI3: D-Link TX530+ NIC (disabled in Win98SE)
OS1: Win98SE(very lean, only Creamware stuff)
OS2: WinXPPro

[OPTIMISATIONS]
MSDOS.SYS: DoubleBuffer=0
SYSTEM.INI: VCache Min & Max set to 32768
WAD on MCI: disabled (enabling this seem to have eliminated the problem on the MSVCRT.DLL)
VMem: 1024MB on the 2GB partition C:
BIOS/Drivers: latest BIOS and drivers for MoBO, SCSI controller, video, and other components.

I'm not certain wether setting a fixed cache buffering and/or disabling DoubleBuffer could cause this? Although, I get a Wordclock drop if I don't tweak these parameters - another story for another day...

Anyhow, any suggestions are much obliged!

Skoal!
The Z Station
thezstation@netzero.net

kimgr · Post by **kimgr** » Wed Apr 17, 2002 3:49 pm

I had the exact same problem on a clients PC with a Pulsar II card:
No matter what I did, after installing Pulsar software, this error would come up. Sometimes right away, sometimes the next day after 50 cold'n'hot reboots. This was on an AMD 1.3 machine with Asus A7M-266 (Or something like that, the one with mixed AMD/Via chipset and DDR-ram).
I figured that there had to be something wrong with the motherboard or the memory, so I send it back to the supplier, got it back a few days later with new motherboard, ram and CPU... Same problem !!!
So now, being really pissed off about spending so much time on one setup, I swapped the hole thing for an Intel based setup exactly the same as my own: Asus CUSL2-C, P3 866, and branded PC133 ram... Same Fu"%#¤" thing !!!
I did the entire install procedure again, but this time I ran hour-long test after each small step:
Install Windows
Update Windows
Install chipset drivers
Install DirectX
Install ATA drivers
Install GPU drivers
Apply Tweaks
And for the grand finale: Install Pulsar software and drivers... And that's where it went wrong again.
Pulsar 3.0 worked fine, but as soon as I updated to 3.01, the error came back ???
I even tried replacing the corrupted system files, but Pulsar 3.01 would simply destroy them again ???
The Client is now a happy Pulsar 3.0 user, looking forward to SFP 3.1

I haven't seen this problem on my own or any other system, but maybe that's because I used a 3.01 installer CD instead of updating from 3.0 ???

Kim.

Spirit · Post by **Spirit** » Wed Apr 17, 2002 5:26 pm

I swapped to a new P4 machine and XP (but used the same install files) and the problem has gone - hopefully never to return.

There were too many of these sorts of errors for it to be something "personal" - must be some sort of deep bug. Pity no one can discover what !