Pulsar keeps crashing on exit

Spirit · Post by **Spirit** » Mon Oct 15, 2001 3:13 am

This problem is steadily getting worse. At first V3 was rock steady, but now it keeps crashing on exit.

Norton Crashguard told me this much, but what does it mean? Any ideas?

Windows 98 Version 4.10.1998

PULSAR.EXE caused fault #c0000005 in BASE.DLL at address 0177:100d2e15
Registers:
EAX=039f5ac0 CS=0177 EIP=100d2e15 EFLGS=00010206
EBX=01e5f870 SS=017f ESP=0065e9b0 EBP=01e5f884
ECX=039f5ac0 DS=017f ESI=00000022 FS=2277
EDX=10102b68 ES=017f EDI=039f5ac0 GS=0000
Bytes at CS:EIP:
8b 4f 38 85 c9 0f 84 a7 00 00 00 8b 11 33 c0 85
Stack dump:

00000028 00000022 01e5f870 100def8b 01e5f870 01e5c3f0 00000000 01e5f870 78001390 01e5c4c0 01e5a810 01e5f870 81b44f7c 01e5a810 780012b1 78037118

ronaldmeij · Post by **ronaldmeij** » Mon Oct 15, 2001 3:53 am

yep same thing here !

But i made a clean install again and now it rock solid again..

dont know whats wrong but its gone for now.

Micha · Post by **Micha** » Mon Oct 15, 2001 4:27 am

Error 5 is segmentation fault, usually behind this message is a not initialized adressing in memory, also known as "pointer to nirvana". Windows protects himself by killing these ones. Understandable, is'nt it?
The wrong pointing, in this case, has to do with pages.
A program has a page=a slice of memory and another has another page. See the danger of confusion? the NT-kernel handles this now pretty good, but the DOS-based kernels had difficulties. That is why in the future there will be only NT-kernels.
For NT: The message is worth to be checked. The adresses tell the programmer by his map-data (a table that lists all entry points into the "working units") where to look.
W98: well, hmm... could be... eventually.
working units: imagine a program as a collection of units, all doing something different. Like, if you choose a function in the menu file -> save as... you give direction to the unit, that works for the purpose of saving a file and, before that, asking the user to give instruction where and under what name. OK?

Happy pulsaring
Micha

Michaelj · Post by **Michaelj** » Mon Oct 15, 2001 10:28 am

Hi I run MAC, but I have had the same problem earlier with the V 2.04.

I solved it like this.
(like always I do backup of the complete installation).

In the folder Pulsar/app/bin
there is a file called cset.ini
I replaces that file with the one from my backupfolder.
everything worked fine.

The V 3 rocks fine, no broblems, so far

Post by **garyb** » Mon Oct 15, 2001 11:21 pm

i've had problems with programs that run in the background, especially macafee and norton products like crashguard.

Zer · Post by **Zer** » Tue Oct 16, 2001 6:44 am

just check also the tipps & tricks forum.

Probs regarding to startup programs could be solved by msconfig. Since Pulsar requires a huge amount of ram, simply disable the startup programs. The computer will start up faster.

Spirit · Post by **Spirit** » Tue Oct 16, 2001 7:13 pm

I've done a defrag and slimmed down the start-up and things are looking a bit better. Thanks

fra77x · Post by **fra77x** » Mon Oct 29, 2001 2:54 pm

I have the same problem any solution
is it safe to replace the cset.ini?

subhuman · Post by **subhuman** » Mon Oct 29, 2001 3:43 pm

Spirit, why are you still using Win98 old? Lots of problems, that is one of THE most unstable OS's microsoft has released.

Try Win98 Second Edition - Windows 98 2nd Ed. 4.10.2222a - or higher.

I love WinME, because it loads everything faster, and I have fixed all the 'issues' with some heavy-handed tweaking and mods

Spirit · Post by **Spirit** » Tue Oct 30, 2001 12:19 am

I didn't even know it was ! The computer was supplied to me so I didn't pay much attention. Can go to SE straight over the top ?

(This might also explain some bad errors I'm also getting with Fireworks V4?)