LCSims
10-01-2016, 21:13
Hi everyone!
Choosing thread titles can be a lot like choosing variable names, you never know how well they will work. I ran into a situation last night where my chosen variable name caused thinBasic to CTD, with a reference to "Fault Module Name: OLEAUT32.DLL". After about an hour of trying to figure out why a simple read a text file, reformat and write to disk kept bombing, it all came down to the variable name in the line of code. I have no idea why Windows 7/64 does not like the name "latBLC" (without the quotes), but it doesn't. Line above uses the variable name "lonBLC' and it processes?!?
So I changed the variable to be a different name and the code works just fine. Ah the wonders of Mr. Bill's operating system, frustrating users for 25 years+.
File can be grabbed at www.lcsims.com/misc/erosCrash.zip (Eros, if you'll let me know when you've had a chance to download?)
I've got the workaround, different name, was just curious why something so benign would bomb Windows?
Lance
Choosing thread titles can be a lot like choosing variable names, you never know how well they will work. I ran into a situation last night where my chosen variable name caused thinBasic to CTD, with a reference to "Fault Module Name: OLEAUT32.DLL". After about an hour of trying to figure out why a simple read a text file, reformat and write to disk kept bombing, it all came down to the variable name in the line of code. I have no idea why Windows 7/64 does not like the name "latBLC" (without the quotes), but it doesn't. Line above uses the variable name "lonBLC' and it processes?!?
So I changed the variable to be a different name and the code works just fine. Ah the wonders of Mr. Bill's operating system, frustrating users for 25 years+.
File can be grabbed at www.lcsims.com/misc/erosCrash.zip (Eros, if you'll let me know when you've had a chance to download?)
I've got the workaround, different name, was just curious why something so benign would bomb Windows?
Lance