base.dll error with fresh V3 Install--?

The Z Station · Post by **The Z Station** » Wed Apr 17, 2002 5:39 pm

Well, after having that dreaded message this morning, I re-installed 3.01. Okay, after a long day at work... I got home..... Of course, the first thing I did was turn my computer on... Then, I was waiting, almost looking forwared to that "Illegal Operations" message on base.dll again... Lo and behold, nada! I loaded tripleDAT 3.11b which loads Pulsar.... It was a go! I performed my testing... Playback multiple tracks, record, whatever -- Stellar! So far, so good and, I hope it stays this way! This is just too peculiar!

What's baffling is that I've never had this problem before. My suspect lies on DX8.1. Although Pulsar 3.01 works magnificently on my dual boot XP Pro using DX8.1, I'm not sure that Win98SE handles it the same way....

I'm reverting back to DX7. The thing is, the current driver on my ATI Xpert 2000 video requires DX8.1, so, I'll have to revert back to its original dirver from the CD-ROM that came with it.

So, as for now, more observations. I'll keep you posted folks....

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

My setup ran without these base.dll errors under 2.04, even though it was running dx8

The Z Station · Post by **The Z Station** » Wed Apr 17, 2002 7:43 pm

The thing is, I started with Pulsar 3.0, I didn't have this problem before then and even with v3.01. It only started after I clean installed Win98SE and with just the Creamware stuff last weekend. The only problem I had then was an occassional wordclock drop when recording on tripleDAT... That's when I decided to dualboot my PC with Win98SE as the host for tripleDAT and Pulsar and very lean OS (no network agents, etc.), and XP Professional which has everthing (network, Pulsar 3.01 <just for basic sound>, and backup programs). Pulsar 3.01 works fine under XP Pro yielding no Illegal Operations error....
In the hopes of troubleshooting my wordclock quandaries, after my mods and all, I then am getting this error....
But, after reinstalling v3.01 this morning, seems that things are working fine now.... So far.... We'll see....

Thanks for the tip!

Looking forward to SF 3.1 I'm glad CW is taking their time though, hopefully no or very minimal bugs...

Skoal!

The Z Station · Post by **The Z Station** » Thu Apr 18, 2002 5:30 am

Greets!

So far, so good! No Illegal/Page Faults on msvcrt.dll and base.dll files! Usually, when I turn the computer on first thing in the morning, I get those messages. Now, they are no more..... hopefully....

[RESOLUTION]
Installed v3.01 (again) over the existing directory. No errors since my re-install.

Cheers!

The Z Station · Post by **The Z Station** » Thu Apr 18, 2002 5:32 am

[ADDENDUM]

Same config and still using DX8.1.....
Also, still performing more tests...

Skoal!
Z

The Z Station · Post by **The Z Station** » Thu Apr 18, 2002 5:21 pm

So far everything is running smoothly! No errors! Been using it since last night and it seems to be rock solid! Cool beans!

Skoal!
The Z Station

JD · Post by JD » Fri Apr 19, 2002 5:55 pm

I tore my hair out for a week and a half on this base.dll thing. Fresh installs, installation priority of drivers ect. I finally gave up. Started my machine one morning, loaded pulsar and just for the hell of it tried loading the pulsar mixer—WHAT—it loaded. Built my standard mixing project and worked for several hours. However, I still get the error on occasion when trying to load a saved project which includes pulsar mixer. If I get the error I immediately reboot which seems to help the problem. I usually can load the project then. I really don’t know why it is so sporadic. Some times it seems to help to have a minimal startup base project and once loaded, set the sample rate to master ( I have two adat connections to a Mac, but if the Mac is off and I load a project which has pulsar slaved I seem to get the error) after waiting a minute or so with the base project as master I then load my regular project. This seems to keep the errors to a minimum, but on occasion it likes to make a cameo appearance.

Keep the posts coming on new info pertaining to this error. Perhaps this post will die with the forthcoming 3.1

Cheers
JD

The Z Station · Post by **The Z Station** » Mon Apr 22, 2002 7:50 am

Mr. JD!

This is a very peculiar anomaly. I was getting that AND an error on the MSVCRT.dll file. AND, this is on a VERY LEAN Win98SE with only tripleDAT 3.06/3.11b and Pulsar 3.01. With minimal Windows drivers and componets, you would think that this will make a cozy host for CW. But, I get those sporadic Page fault errors on those dll files.
The thing is, too, I never had those problems on my last setup...
For the past 4 days, after reinstalling 3.01 on top of the existing install, the error has not showed itself. It's been very stable (so far) and performing very well, In fact, I just finished my first session on this config with a very smooth result.

I hope you are right that the release of 3.1 will finalise this thread....

Best wishes!
Z

subhuman · Post by **subhuman** » Mon Apr 22, 2002 8:36 am

Are you using generic RAM?

JD · Post by JD » Mon Apr 22, 2002 11:06 am

I did invest in 512 of crucial memory. On their website they allow you to chose your Motherboard and it gives you the results for proper memory. I put in the pc133. Seemed to decrease the frequency of errors but not abolish them completely.

Asus Cusl-2

ohmelas · Post by **ohmelas** » Thu May 02, 2002 7:56 pm

dll hell....

check out this site for comic relief:

http://www.ssw.com.au/SSW/Database/DLLHell.asp

This page will outline the most recent base.dll file:

http://support.microsoft.com/servicedes ... ?Id=173558

If you're looking for specific support on these dynamic link library files check out microsofts dll help site. They are a wealth of resources:

http://support.microsoft.com/servicedes ... n/help.htm

I seemed to have had this problem on my old system.

I was using a BP6 MOBO with dual Celeron 500s and two IDE66 hard drives with cheap PC100 RAM and two graphics cards.

It was the very reason why I upgraded to a P4 even though they were overpriced at the time. I had a Via chipset. I had PC100 generic RAM. I was using Windows 98 and had just recently installed the lastest version of Cakewalk with the Latest Version of Direct X.

My solution was as follows:

1. Turn the old system into a file server.
2. Buy a non VIA chipset MOBO. I850 w/ 4 layered (not the two as in generic) top-notch RAMBUS ram!
3. Ditch Cakewalk and Direct X for VST and Cubase.

The cost for the overall upgrade was around $1000 but I was a very very happy man and have not had any kinds of those problems.

I hope that this is helpful. The problem is not with Windows. Make sure that you also do the appropriate tweaks on the Matrox card since Cream Ware is really sensitive about those things.

Do all the Windows 98 tweaks suggested by Sub.

Problems will dissappear. I'm living proof.

_________________
Ravenwhite Productions
Digital Recording Studio
Milwaukee, WI USA
http://ohmelas.tripod.com/ravenwhitepro ... index.html
****************************
Two-Week-Endz, 40 Hours $995

<font size=-1>[ This Message was edited by: ohmelas on 2002-05-02 21:09 ]</font>

The Z Station · Post by **The Z Station** » Fri May 03, 2002 8:38 am

Updates:

I hate to keep beating the "dead horse" but...

After reinstalling Win98SE, things are running much better - at least those error reports doesn't pop up as much as it used to (certainly doesn't cause an error during bootup anymore!). Also, I found out, too, that manually starting Pulsar and tripleDAT separately (3.06), Pulsar doesn't crash - at least, it hasn't yet (this after a few dozen tests - sounds good so far!). No word clock drop either!

Any other tripleDAT afficionados here?