Ffff. I would guess it's not really an operating system specific problem. I can only test on Win7-64 right now though. Not sure how to proceed unless I can get the crash to happen for me.
Here's an EXE that will pop up a series of message boxes that say "Debug point #" as you try to open an NSF. Could somebody who is crashing tell me how far it gets before it crashes?
*** Edit: removed link. I think the usefulness of this test has been exhausted.
Edit: Also, is there a minidump / crash dump / anything like that?
No crash dump is generated; the program simply hangs and does not respond to any user input right after selecting which NSF to import. Task manager is required to end the process.
Don't worry; as long as you tell rainwarrior the debug point #, he'll know where to look.
I tested on XP Pro SP3 with 1.6 GHz single-core CPU & 1 GB of RAM; no crashes here. I've gone through 7 debug points & still succeeded in importing a song.
Shywolf & tadpole; what OS are you guys using?
_______________________
Technology: the one thing that's hated & cursed at by all engineers, technologists, scientists & technicians!
Hmm... Alright; let's make an official method of reporting things to rainwarrior.
First off, let's start by OS, RAM & CPU specs. Then, let's actually tell rainwarrior at what exact point does the program crash. Using rainwarrior's debug test would be a good place to start. Run it, import an NSF & report exactly what was the last number to appear before a crash.
With me, I have no problems under XP SP3 whatsoever. Everything works just fine for me & you already have my specs. I just want to make things easier for rainwarrior.
_______________________
Technology: the one thing that's hated & cursed at by all engineers, technologists, scientists & technicians!
Umm, Tech, I know you're trying to help, but this arbitrary set of instructions is not necessary or wanted. The things I want to know I have asked. People telling me their operating systems is not going to help, people telling me they don't crash doesn't help, and really the "Debug point #" build will not be of any further use unless someone crashes at a different point than Shywolf, which I kinda doubt will happen.
