|When re-booting ( ironically, to try to speed 4.21b up )|
win 2k pro sp3 ( recently installed vis studio .net , with 30 megs of security upgrades - maybe that's stuffed things).
Unhandled exception at 0x00404d33 in muon1_background.exe: 0xC0000005: Access violation reading location 0x00000000.
[This message was edited by Stephen Brooks on 2002-Aug-22 at 11:54.]
|oh, OK, so I renamed auto.sav and it seems to be going ( hope it is faster and more consistent though).|
|You renamed auto.sav to what? Was this to stop the program from reading it or something? I guess if you shut down while the program was (by chance) in the middle of an autosave you'd get a corrupt auto.sav that needs removing.|
"As every 11-year-old kid knows, if you concentrate enough Van-der-Graff generators and expensive special effects in one place, you create a spiral space-time whirly thing, AND an interesting plotline"
|confused ?? well, what can you expect from a bird brain??|
I was following the sugestion of Jim Reed in 'Muon 4.21b crashed....'
Rename it to anything ( auto.sav.bak ) should mean the prog cant see it, and just create a new one ( if it is set up to do that, which obviously it is ...).
anyway, it seems to be working, so umm, I guess all is OK ?
|I'd imagine so. All I can hope is that this bug is either one of those I've removed in the current development towards 4.22, or is something not specifically to do with my particular program (computer having a bad day etc.) .|