MicroCodeStudioPlus keeps crashing.

[picster]

Just crashed - so much for the italics theory. HOWEVER, this was STILL a case of crashing while I was typing in a comment field, which ALWAYS seems to be the case. (cross-posted)

[Ioannis]

Hmm, Comments are necessary of course. What if you type the comments this way:

keep typing WITHOUT the ; or ' and after finishing typing get back to the first character and type the ; or ' symbol.

Not the best idea but maybe it will help until the problem is solved.

Ioannis

[picster]

This is still happening. It seems to come in fits and spurts, no issues for a couple of weeks, then bam, crash after crash of the program. Excessively annoying, particularly when there's no time-based autosave built-in. Yesterday I had about 8 program crashes before I walked away.

Has anyone experiencing this incessant problem tried any of the following and STILL had a MCSP crash:

1) running it as the ONLY program? I usually have a couple of other programs running (typically have a web browser open as well as a PDF for the PIC I'm using)

2) disconnecting from the internet and running only while disconnected? Keeps other programs from doing their own online thing?

3) concurrent with #2, disable Microsoft Security Essentials (or other)?

I'm thinking of doing all 3 at once to see if it possibly helps.

This is paid software, and it's utter *BS* that this should be an issue for a number of people who have paid to use it and are being plagued with this problem. I know it's *not* an MELabs product, but perhaps MELabs could step in and put some pressure on since it's a "cooperative" product that's advertised for use with PBPx (hence pointing there for sales).

[Archangel]

This is paid software, and it's utter *BS* that this should be an issue for a number of people who have paid to use it and are being plagued with this problem. I know it's *not* an MELabs product, but perhaps MELabs could step in and put some pressure on since it's a "cooperative" product that's advertised for use with PBPx (hence pointing there for sales).

You know how difficult it is to write a program for a pic and have it work, ALWAYS work for your specific PIC which has NO OTHER programs working the background. Any program you write for a PIC is a thousand times more simple than any program running on a PC
Now Imagine your program must run on every PIC without modification, while other programs demand the same resources.
There are application and programs that do not play well with others, especially anti virus software. You can do things to assist MCS, like give it higher permissions than some other programs, also change the mode it's running in WIN ,XP,98 etc. In this case BS might mean Better stratagy In ANY event getting mad or frustrated is anti useful.
sometimes Youtube crashes our computer Full on BSOD and no other ap does this.

[picster]

You know how difficult it is to write a program for a pic and have it work, ALWAYS work for your specific PIC which has NO OTHER programs working the background. Any program you write for a PIC is a thousand times more simple than any program running on a PC
Now Imagine your program must run on every PIC without modification, while other programs demand the same resources.
There are application and programs that do not play well with others, especially anti virus software. You can do things to assist MCS, like give it higher permissions than some other programs, also change the mode it's running in WIN ,XP,98 etc. In this case BS might mean Better stratagy In ANY event getting mad or frustrated is anti useful.
sometimes Youtube crashes our computer Full on BSOD and no other ap does this.

Perhaps without the benefit of context and reviewing the history of background postings, my prior post might seem disrespectful or overly judgmental.

A couple of things of note here for your consideration. First, I'm not attacking MELABS software. PBP itself is, and always has been, in my experience, reliable, responsive and supportive to users who report bugs or problems. My beef is not with MELABS' product. For me, this development system was an investment for small business. I've owned PBP for years, and faithfully upgraded to keep current a number of times.

The second item I would like to point out is that many of us who use PBP also have experience with computer programming for Windows, and the compatibility speech is therefore somewhat unnecessary. There are simple rules of thumb to follow for maximizing compatibility with users' systems during development, and I'm sure I don't need to expand on that because it would be an exercise in redundant information to any experienced programmer. I have personally had this issue on three different computers each with a different CPU and differing video hardware, and I've fiddled and messed with settings ad nauseam so it's not like I haven't tried to do what I can to make things better on my end.

Thirdly, my "calling BS on Mecanique" and hoping for some intervention from MELABS is a last resort after literally YEARS with this known problem being experienced by numerous programmers here, some of whom are quite prolific, well respected in the PBP community, and senior in rank. I have personally posted about this several times, in more than one forum topic on the subject, to no avail, in hopes of getting some help (as have others). The official Mecanique line seems to be "I can't replicate the problem". It is my hope that someone with some leverage steps up to the plate here. The comparison to YouTube implies that I should expect the same level of reliability in a paid product that I use for small business as I get from a free product that I use for entertainment. One might consider such a comparison, to be "anti-useful, and in the same boat as the systematic lack of validation regarding a repeatedly documented problem that continues to be lurking for people who are merely trying to develop products using a MELABS product in concert with a MELABS promoted development tool by others. Again, it's not like I haven't tried here, as have others. If you can sense frustration, then it's for a good reason. But it's taken a long journey to get to this point, which I believe may have either been overlooked, or perhaps it's merely information that you've not been privy to.

I trust this helps to clarify that I recognize the challenges and lines of delineation here. My point is, Mecanique doesn't seem to be actively pursuing any resolve, and in my estimation it doesn't reflect well on MELABS who continue to flog a sister product that they don't support (and that seems poorly supported by the developer, in that this issue has gone unresolved for years with no sign of change, to the point of some people altogether abandoning their paid software for other alternatives). It was my hope that MELABS could step up and try to move things forward, considering the history and the continued lack of viable solution. After all, it would only serve to support and help MELABS customers who are loyal to their product base.

[Dave]

I'm Sorry but I believe there is something else that is loaded on your machines that is creating the problems. I have used MCS since back when PBP2.6 was around (even before this thread was started) and have used MCPX since PBP3.0 shipped. I now use MCSPX with PBP 3.1 and have NEVER had MCSPX or and previously available version crash. I currently have licenses for and loaded on 1 XP machine 2 Windows 7 machines and 1 Windows 10 machine. Maybe you all should start looking somewhere else for the problem. IMHO...

[Ioannis]

Does this problem happen also in Windows safe mode?

Ioannis