MCS is Crashing

[Demon]

Mark, sorry I missed this thread back in March.

I would have been curious to know what would have happened if you editted that bad line in NOTEPAD, and then compiled that from MCS.

Notepad removes all formatting.

Robert

[tumbleweed]

I would have been curious to know what would have happened if you editted that bad line in NOTEPAD, and then compiled that from MCS

Not much. Any formatting like fonts, colors, or italics is strictly in the IDE display. The source files are already plain-text.

[mark_s]

Hi Robert, it's actually Picster that beleives the crashing is from using italics in the IDE. I was trying to change a DEFINE OSC statement and every time I hit a key it would crash. This happened only to the file from my flash drive. I could edit files on my hard drive? I switched to non italics, just in case this actually is the cause.

I think a real test would be to leave italics checked. When a crash occurs switch to non-italics and see if it stops.

If you read through both threads on this subject. You will find there is no pattern or consistancy, so difficult to trouble shoot.

[MichelJasmin]

Do you copy some text from the datasheet PDF and then paste to MCS? Not sure but I used to had crashes when doing it...

[picster]

Do you copy some text from the datasheet PDF and then paste to MCS? Not sure but I used to had crashes when doing it...

Maybe the windows clipboard is including the font formatting and it's also messing up the in-line font processing?

[Demon]

I just did a test on Windows 10 64bit home edition. I always used italics and colours for comments with Win XP 32bit, Win7 64bit and now Win10 64bit (default MCSP settings), never a problem.

Copied in text from PDFs, made them comments, compiled no problem.
Copied in fuse settings and made them code, compiled no problem.

I checked my MCSP shortcut, I do not run it as administrator or any other compatibility setting.

There must be more involved, we're still missing something.

Robert
MCSP v5.0.0.5
PBPX v3.0.8.4

[picster]

I just did a test on Windows 10 64bit home edition. I always used italics and colours for comments with Win XP 32bit, Win7 64bit and now Win10 64bit (default MCSP settings), never a problem.

Copied in text from PDFs, made them comments, compiled no problem.
Copied in fuse settings and made them code, compiled no problem.

I checked my MCSP shortcut, I do not run it as administrator or any other compatibility setting.

There must be more involved, we're still missing something.

Robert
MCSP v5.0.0.5
PBPX v3.0.8.4

Compiling has never caused problems for me, NEVER had any when sitting idle, and ***always always always WHILE TYPING!!!*** This strongly suggests to me that there's some issue with processing the keystrokes, and the text on the screen is obviously continuously "reassessed" to display it in the configured font/color. That's my "working theory". As I recall, there was a suggestion about video drivers as well, a while back - Nvidia being questioned as potentially part of the issue, but I couldn't test it on a non-Nvidia machine (although I tried running with my alternate "slow" graphics card on the dual-graphics equipped machine and it still crashed).

[Demon]

i have only one idea, did you install MCSP and PBP as administrator?

I might have, don't remember. It might be possible for the install to be incomplete if the installation package did not have necessary admin rights. I do know several software have varying levels of problems with Win10.

I just cannot install properly PaintShop Pro XI using Win10 64bit. Looks like I'll be forced to bite that bullet and get and upgrade even though I am very content with that old version.

Robert

[picster]

Hi Robert, it's actually Picster that beleives the crashing is from using italics in the IDE. I was trying to change a DEFINE OSC statement and every time I hit a key it would crash. This happened only to the file from my flash drive. I could edit files on my hard drive? I switched to non italics, just in case this actually is the cause.

I think a real test would be to leave italics checked. When a crash occurs switch to non-italics and see if it stops.

If you read through both threads on this subject. You will find there is no pattern or consistancy, so difficult to trouble shoot.

Note that a DEFINE statement is also likely in a specified "different" font/color, causing it to be processed "on the fly" as you're typing... same problrem, different manifestation. Were you using italics for Defines?

[Demon]

I've always used default MCSP settings.

My laptop used is a HP Pavillion i5 Intel/nVidia.

I'll try later typing a long-winded comment and see how that goes.

Robert

[Demon]

Nope, long-winded comments, a DEFINE OSC 10 thrown in, more comments, no problem.

Robert

[picster]

Nope, long-winded comments, a DEFINE OSC 10 thrown in, more comments, no problem.

Robert

Perhaps I'm not approaching this with the same attack...

If this was a "sure thing" that ALWAYS happened, it would be pretty easy to resolve. However, my experience is it's very hit and miss - hence I don't believe a crash can be "forced", there are other undetermined variables involved, but... again... because it ALWAYS when I'm typing, I believe that says something. It can sit idle for DAYS and nothing happens. I'm wondering if others who are experiencing this can avoid crashes by trying this change, thereby contributing to the validation of the theory - not try to FORCE another crash when it's unpredictable and not a "sure thing".

[Demon]

Well then, I guess I'll just keep an eye open and report back f anything happens. But MCSP has never bombed on me in over a year on this laptop.

I honestly cannot see how graphic drivers have anything to do with data entry, especially in software that emulates Notepad (no special characters).

But then again, my specialty was mainframe programming. I only program PCs when I sleep at the Holiday Inn.

Robert