Hi peter, I had similar problems with Win 7 about a year ago, I could
never determine if it was IAR the cause. I hate Win 7 anyway, so after 2
tries I just reverted back, that doesn't help, but there are people
running IAR on win 7 I believe, so it should go. I just couldn't be
arsed to persevere with something I consider broken anyway.
Al
On 14/08/2012 4:34 PM, Peter Grey wrote:
> I posted this problem some weeks ago. I moved to a
Windows 7 computer
> some months ago and have been having all sorts of problems with IAR
> kickstart. Whenever I turn off the computer I have to remove the program
> entirely and reload it. Now it is locking up a number of times a day.
> Has anyone experienced such problems? I am using FET_611 which loads as
> version 5.40.6. I even have problems saving some programs when running
> this. It is as though I have a virus but I have checked it out and
> nothing is there. It is becoming really frustrating. I have tried
> different USB ports, different MSP-FET modules and it is all the same.
>
> Any help is appreciated.
>
> Peter
>
Problems with IAR Kickstart
Started by ●July 18, 2012
Reply by ●August 14, 20122012-08-14
Reply by ●August 14, 20122012-08-14
On 14 Aug 2012, at 19:44, Jon Kirwan wrote:
> On Tue, 14 Aug 2012 17:32:09 +0100, you wrote:
>
>>> Short answer -- no, I've not tried it yet. I could (and
>>> might) if IAR were interested in the results of the test. But I don't
>>> expect them to be, unless their paying customers are.
>>> And it really should come from that direction. I haven't bought a license,
>>> since I only use the MSP430 for hobby work and teaching students right
>>> now.
>>
>> TI usually make the mess, not tools vendors. TI are responsible for FET
>> firmware, USB hardware, USB compliance, and driver software. Sometimes,
>> things just don't work and tools vendors get stuck with the problem.
>
> That could fit the facts. All of my other tools work just
> fine on USB (such as Microchip... and I have thousands of
> dollars of Microchip equipment here.) I don't have a problem
> with any other micro I've working on in the last year and a
> half on this machine. IAR kickstart is the only case I have
> personally experienced.
>
> Do you have a way I could verify the problem as being TI's?
> For example, some other software tool (in limited, hobbyist
> form) that would use the same TI drivers as IAR's Kickstart?
> If the problem is the same with two completely different
> toolsets, but the same TI software, then that would strongly
> support this thought.
You can always install Code Composer Studio. That's all TI. However, there is a 3P mailing list for the DLL and tools and some 3Ps have a rant now and again.
-- Paul.
> On Tue, 14 Aug 2012 17:32:09 +0100, you wrote:
>
>>> Short answer -- no, I've not tried it yet. I could (and
>>> might) if IAR were interested in the results of the test. But I don't
>>> expect them to be, unless their paying customers are.
>>> And it really should come from that direction. I haven't bought a license,
>>> since I only use the MSP430 for hobby work and teaching students right
>>> now.
>>
>> TI usually make the mess, not tools vendors. TI are responsible for FET
>> firmware, USB hardware, USB compliance, and driver software. Sometimes,
>> things just don't work and tools vendors get stuck with the problem.
>
> That could fit the facts. All of my other tools work just
> fine on USB (such as Microchip... and I have thousands of
> dollars of Microchip equipment here.) I don't have a problem
> with any other micro I've working on in the last year and a
> half on this machine. IAR kickstart is the only case I have
> personally experienced.
>
> Do you have a way I could verify the problem as being TI's?
> For example, some other software tool (in limited, hobbyist
> form) that would use the same TI drivers as IAR's Kickstart?
> If the problem is the same with two completely different
> toolsets, but the same TI software, then that would strongly
> support this thought.
You can always install Code Composer Studio. That's all TI. However, there is a 3P mailing list for the DLL and tools and some 3Ps have a rant now and again.
-- Paul.
Reply by ●August 14, 20122012-08-14
On 14/08/2012 5:50 PM, Arie de Muynck wrote:
Can you tell me where you make these changes?
Thanks
Peter
> On 14/08/2012 3:37 PM, Onestone wrote:
>> I must admit that I do not like Windows 7 either. It seems to store things
>> away in places only it knows!! I had to upgrade because of other software.
>> It looks like I may need to go back tp XP for the IAR software.
>
> Peter,
>
> I’ve had similar problems with Win7 running older SW. Apparently some try to
> (need to) write in the “C:\Program Files” directory which is not allowed by
> UAC.
> Since I consider Windows unsafe anyway, I just changed permissions for that
> and underlying directories to “R/W for Everyone” and most problems
> disappeared.
>
> Regards,
> Arie de Muynck
>
>
Can you tell me where you make these changes?
Thanks
Peter
> On 14/08/2012 3:37 PM, Onestone wrote:
>> I must admit that I do not like Windows 7 either. It seems to store things
>> away in places only it knows!! I had to upgrade because of other software.
>> It looks like I may need to go back tp XP for the IAR software.
>
> Peter,
>
> I’ve had similar problems with Win7 running older SW. Apparently some try to
> (need to) write in the “C:\Program Files” directory which is not allowed by
> UAC.
> Since I consider Windows unsafe anyway, I just changed permissions for that
> and underlying directories to “R/W for Everyone” and most problems
> disappeared.
>
> Regards,
> Arie de Muynck
>
>
Reply by ●August 14, 20122012-08-14
On 14/08/2012 9:52 PM, Jon Kirwan wrote:
It sounds just like the problems I am having. I have decided to get a
new laptop this morning and install XP and devote it exclusively to IAR
Kickstart.
Thanks
Peter
> On Tue, 14 Aug 2012 15:04:56 +0800, you wrote:
>
>> I posted this problem some weeks ago. I moved to a Windows 7 computer
>> some months ago and have been having all sorts of problems with IAR
>> kickstart. Whenever I turn off the computer I have to remove the program
>> entirely and reload it. Now it is locking up a number of times a day.
>> Has anyone experienced such problems? I am using FET_611 which loads as
>> version 5.40.6. I even have problems saving some programs when running
>> this. It is as though I have a virus but I have checked it out and
>> nothing is there. It is becoming really frustrating. I have tried
>> different USB ports, different MSP-FET modules and it is all the same.
>>
>> Any help is appreciated.
> Yes, I also have had LOTS of problems (still do) with IAR
> Kickstart on Win7 64-bit Ultimate. When I first started using
> the IAR Kickstart on this system, it was brand new "out of
> box" so to speak. I used my MSDN license (yes, I pay
> Microsoft godawful lots of dollars every year, damn them) to
> download a clean Win7 64-bit Ultimate -- so it did NOT come
> from some vendor.
>
> The problems I have are mostly that it won't download code
> and gets locked up in the process and I have to go through a
> nasty process to shut everything down and restart. Sometimes,
> I can do this without completely shutting down. Sometimes, it
> works using different menu options instead of the download
> and debug one. (download-only, for example.) In other words,
> it isn't consistent. But it is consistently problematic.
>
> I simply don't use the new machine with IAR kickstart. That's
> been my answer. I spent way too much time screwing with this
> trying to get it to work. I'm done with that, now.
>
> Jon
>
It sounds just like the problems I am having. I have decided to get a
new laptop this morning and install XP and devote it exclusively to IAR
Kickstart.
Thanks
Peter
> On Tue, 14 Aug 2012 15:04:56 +0800, you wrote:
>
>> I posted this problem some weeks ago. I moved to a Windows 7 computer
>> some months ago and have been having all sorts of problems with IAR
>> kickstart. Whenever I turn off the computer I have to remove the program
>> entirely and reload it. Now it is locking up a number of times a day.
>> Has anyone experienced such problems? I am using FET_611 which loads as
>> version 5.40.6. I even have problems saving some programs when running
>> this. It is as though I have a virus but I have checked it out and
>> nothing is there. It is becoming really frustrating. I have tried
>> different USB ports, different MSP-FET modules and it is all the same.
>>
>> Any help is appreciated.
> Yes, I also have had LOTS of problems (still do) with IAR
> Kickstart on Win7 64-bit Ultimate. When I first started using
> the IAR Kickstart on this system, it was brand new "out of
> box" so to speak. I used my MSDN license (yes, I pay
> Microsoft godawful lots of dollars every year, damn them) to
> download a clean Win7 64-bit Ultimate -- so it did NOT come
> from some vendor.
>
> The problems I have are mostly that it won't download code
> and gets locked up in the process and I have to go through a
> nasty process to shut everything down and restart. Sometimes,
> I can do this without completely shutting down. Sometimes, it
> works using different menu options instead of the download
> and debug one. (download-only, for example.) In other words,
> it isn't consistent. But it is consistently problematic.
>
> I simply don't use the new machine with IAR kickstart. That's
> been my answer. I spent way too much time screwing with this
> trying to get it to work. I'm done with that, now.
>
> Jon
>
Reply by ●August 14, 20122012-08-14
On Tue, 14 Aug 2012 15:04:56 +0800, you wrote:
>I posted this problem some weeks ago. I moved to a Windows 7 computer
>some months ago and have been having all sorts of problems with IAR
>kickstart. Whenever I turn off the computer I have to remove the program
>entirely and reload it. Now it is locking up a number of times a day.
>Has anyone experienced such problems? I am using FET_611 which loads as
>version 5.40.6. I even have problems saving some programs when running
>this. It is as though I have a virus but I have checked it out and
>nothing is there. It is becoming really frustrating. I have tried
>different USB ports, different MSP-FET modules and it is all the same.
>
>Any help is appreciated.
Yes, I also have had LOTS of problems (still do) with IAR
Kickstart on Win7 64-bit Ultimate. When I first started using
the IAR Kickstart on this system, it was brand new "out of
box" so to speak. I used my MSDN license (yes, I pay
Microsoft godawful lots of dollars every year, damn them) to
download a clean Win7 64-bit Ultimate -- so it did NOT come
from some vendor.
The problems I have are mostly that it won't download code
and gets locked up in the process and I have to go through a
nasty process to shut everything down and restart. Sometimes,
I can do this without completely shutting down. Sometimes, it
works using different menu options instead of the download
and debug one. (download-only, for example.) In other words,
it isn't consistent. But it is consistently problematic.
I simply don't use the new machine with IAR kickstart. That's
been my answer. I spent way too much time screwing with this
trying to get it to work. I'm done with that, now.
Jon
>I posted this problem some weeks ago. I moved to a Windows 7 computer
>some months ago and have been having all sorts of problems with IAR
>kickstart. Whenever I turn off the computer I have to remove the program
>entirely and reload it. Now it is locking up a number of times a day.
>Has anyone experienced such problems? I am using FET_611 which loads as
>version 5.40.6. I even have problems saving some programs when running
>this. It is as though I have a virus but I have checked it out and
>nothing is there. It is becoming really frustrating. I have tried
>different USB ports, different MSP-FET modules and it is all the same.
>
>Any help is appreciated.
Yes, I also have had LOTS of problems (still do) with IAR
Kickstart on Win7 64-bit Ultimate. When I first started using
the IAR Kickstart on this system, it was brand new "out of
box" so to speak. I used my MSDN license (yes, I pay
Microsoft godawful lots of dollars every year, damn them) to
download a clean Win7 64-bit Ultimate -- so it did NOT come
from some vendor.
The problems I have are mostly that it won't download code
and gets locked up in the process and I have to go through a
nasty process to shut everything down and restart. Sometimes,
I can do this without completely shutting down. Sometimes, it
works using different menu options instead of the download
and debug one. (download-only, for example.) In other words,
it isn't consistent. But it is consistently problematic.
I simply don't use the new machine with IAR kickstart. That's
been my answer. I spent way too much time screwing with this
trying to get it to work. I'm done with that, now.
Jon
Reply by ●August 14, 20122012-08-14
On Tue, 14 Aug 2012 17:04:52 -0000, you wrote:
> On my Win7-64 Ultimate system I was seeing hundreds of
> failed load attempts for the TI FET dll, which seemed linked
> to occasional crashes for the OS. And, when trying to load
> and debug programs in IAR the system would lock-up as well
> as multiple reboots of the USB ports. (I've got both OEM USB
> 2.0 & 3.0 ports and an add-in 3.0 card). I've since gone
> back to using an older XP laptop for my occasional coding
> projects, and removed the offending TI dlls. IAR is still
> installed, but no further problems since removing the TI
> dlls...
That's a decent description of my experiences.
> It does appear that TI and the Win 7 USB implementations are
> not happy with each other.
> Not a solution to Peter's original question, but maybe
> something of use???
No idea, but the fact is that all of my other tools work just
fine on USB (such as Microchip... and I have thousands of
dollars of Microchip equipment here.) I don't have a problem
with any other micro I've working on in the last year and a
half on this machine. IAR kickstart is the only case, so far.
Jon
> On my Win7-64 Ultimate system I was seeing hundreds of
> failed load attempts for the TI FET dll, which seemed linked
> to occasional crashes for the OS. And, when trying to load
> and debug programs in IAR the system would lock-up as well
> as multiple reboots of the USB ports. (I've got both OEM USB
> 2.0 & 3.0 ports and an add-in 3.0 card). I've since gone
> back to using an older XP laptop for my occasional coding
> projects, and removed the offending TI dlls. IAR is still
> installed, but no further problems since removing the TI
> dlls...
That's a decent description of my experiences.
> It does appear that TI and the Win 7 USB implementations are
> not happy with each other.
> Not a solution to Peter's original question, but maybe
> something of use???
No idea, but the fact is that all of my other tools work just
fine on USB (such as Microchip... and I have thousands of
dollars of Microchip equipment here.) I don't have a problem
with any other micro I've working on in the last year and a
half on this machine. IAR kickstart is the only case, so far.
Jon
Reply by ●August 14, 20122012-08-14
Jon, I have not used Win7 64bit yet, but in 32bit versions some times it
helps to run the program in the virtual win-XP machine; have your tried this?
M.
Jon Kirwan :
> On Tue, 14 Aug 2012 15:04:56 +0800, you wrote:
>
>>I posted this problem some weeks ago. I moved to a Windows 7 computer
>>some months ago and have been having all sorts of problems with IAR
>>kickstart. Whenever I turn off the computer I have to remove the program
>>entirely and reload it. Now it is locking up a number of times a day.
>>Has anyone experienced such problems? I am using FET_611 which loads as
>>version 5.40.6. I even have problems saving some programs when running
>>this. It is as though I have a virus but I have checked it out and
>>nothing is there. It is becoming really frustrating. I have tried
>>different USB ports, different MSP-FET modules and it is all the same.
>>
>>Any help is appreciated.
>
> Yes, I also have had LOTS of problems (still do) with IAR
> Kickstart on Win7 64-bit Ultimate. When I first started using
> the IAR Kickstart on this system, it was brand new "out of
> box" so to speak. I used my MSDN license (yes, I pay
> Microsoft godawful lots of dollars every year, damn them) to
> download a clean Win7 64-bit Ultimate -- so it did NOT come
> from some vendor.
>
> The problems I have are mostly that it won't download code
> and gets locked up in the process and I have to go through a
> nasty process to shut everything down and restart. Sometimes,
> I can do this without completely shutting down. Sometimes, it
> works using different menu options instead of the download
> and debug one. (download-only, for example.) In other words,
> it isn't consistent. But it is consistently problematic.
>
> I simply don't use the new machine with IAR kickstart. That's
> been my answer. I spent way too much time screwing with this
> trying to get it to work. I'm done with that, now.
> Jon
helps to run the program in the virtual win-XP machine; have your tried this?
M.
Jon Kirwan :
> On Tue, 14 Aug 2012 15:04:56 +0800, you wrote:
>
>>I posted this problem some weeks ago. I moved to a Windows 7 computer
>>some months ago and have been having all sorts of problems with IAR
>>kickstart. Whenever I turn off the computer I have to remove the program
>>entirely and reload it. Now it is locking up a number of times a day.
>>Has anyone experienced such problems? I am using FET_611 which loads as
>>version 5.40.6. I even have problems saving some programs when running
>>this. It is as though I have a virus but I have checked it out and
>>nothing is there. It is becoming really frustrating. I have tried
>>different USB ports, different MSP-FET modules and it is all the same.
>>
>>Any help is appreciated.
>
> Yes, I also have had LOTS of problems (still do) with IAR
> Kickstart on Win7 64-bit Ultimate. When I first started using
> the IAR Kickstart on this system, it was brand new "out of
> box" so to speak. I used my MSDN license (yes, I pay
> Microsoft godawful lots of dollars every year, damn them) to
> download a clean Win7 64-bit Ultimate -- so it did NOT come
> from some vendor.
>
> The problems I have are mostly that it won't download code
> and gets locked up in the process and I have to go through a
> nasty process to shut everything down and restart. Sometimes,
> I can do this without completely shutting down. Sometimes, it
> works using different menu options instead of the download
> and debug one. (download-only, for example.) In other words,
> it isn't consistent. But it is consistently problematic.
>
> I simply don't use the new machine with IAR kickstart. That's
> been my answer. I spent way too much time screwing with this
> trying to get it to work. I'm done with that, now.
> Jon
Reply by ●August 15, 20122012-08-15
> From: Peter Grey
> Can you tell me where you make these changes?
> Thanks
Hi Peter,
1. If you are not the administrator, first open Windows Explorer, browse to
"C:\Windows\explorer.exe", rightclick, "Run as administrator".
2. In that Windows explorer, browse to “C:\Program Files\”,
right click on that directory, select Properties, select Security, select
"Users", click Edit, select "Users", enable the "Write" tickbox and click
OK. If you are asked if it should apply to all subfolders too, select Yes.
I remember changing the permissions for all in "Program files" but cannot
reproduce that right now in Win7. The properties of the separate program
directories however are editable, and that is where the offending program
tries to write its INI files etc.
Regards,
Arie de Muynck
> Peter,
>
> I’ve had similar problems with Win7 running older SW. Apparently some try
> to
> (need to) write in the “C:\Program Files” directory which is not allowed
> by
> UAC.
> Since I consider Windows unsafe anyway, I just changed permissions for
> that
> and underlying directories to “R/W for Everyone” and most problems
> disappeared.
> Can you tell me where you make these changes?
> Thanks
Hi Peter,
1. If you are not the administrator, first open Windows Explorer, browse to
"C:\Windows\explorer.exe", rightclick, "Run as administrator".
2. In that Windows explorer, browse to “C:\Program Files\”,
right click on that directory, select Properties, select Security, select
"Users", click Edit, select "Users", enable the "Write" tickbox and click
OK. If you are asked if it should apply to all subfolders too, select Yes.
I remember changing the permissions for all in "Program files" but cannot
reproduce that right now in Win7. The properties of the separate program
directories however are editable, and that is where the offending program
tries to write its INI files etc.
Regards,
Arie de Muynck
> Peter,
>
> I’ve had similar problems with Win7 running older SW. Apparently some try
> to
> (need to) write in the “C:\Program Files” directory which is not allowed
> by
> UAC.
> Since I consider Windows unsafe anyway, I just changed permissions for
> that
> and underlying directories to “R/W for Everyone” and most problems
> disappeared.
Reply by ●August 15, 20122012-08-15
On 15/08/2012 2:01 PM, Arie de Muynck wrote:
Firstly, thanks to all who replied. I went out to purchase a computer
and to load Windows XP. When I explained what I intended he suggested
that I change the properties on the IAR program. I right-click on the
IAR icon, select properties and then compatibility tab. Check the
compatibility box (run in Windows XP service pack3) and also the "run
program as administrator" box and then OK. I did this about 4 hours ago
and I have not had one single problem. I will wait a few days to be
absolutely certain. I will be also trying it with Protel 99SE which is
also flaky under Windows 7.
Thanks
Peter
>> From: Peter Grey
>> Can you tell me where you make these changes?
>> Thanks
> Hi Peter,
>
> 1. If you are not the administrator, first open Windows Explorer, browse to
> "C:\Windows\explorer.exe", rightclick, "Run as administrator".
>
> 2. In that Windows explorer, browse to “C:\Program Files\”,
> right click on that directory, select Properties, select Security, select
> "Users", click Edit, select "Users", enable the "Write" tickbox and click
> OK. If you are asked if it should apply to all subfolders too, select Yes.
>
> I remember changing the permissions for all in "Program files" but cannot
> reproduce that right now in Win7. The properties of the separate program
> directories however are editable, and that is where the offending program
> tries to write its INI files etc.
>
> Regards,
> Arie de Muynck
>
>> Peter,
>>
>> I’ve had similar problems with Win7 running older SW. Apparently some try
>> to
>> (need to) write in the “C:\Program Files” directory which is not allowed
>> by
>> UAC.
>> Since I consider Windows unsafe anyway, I just changed permissions for
>> that
>> and underlying directories to “R/W for Everyone” and most problems
>> disappeared.
>
Firstly, thanks to all who replied. I went out to purchase a computer
and to load Windows XP. When I explained what I intended he suggested
that I change the properties on the IAR program. I right-click on the
IAR icon, select properties and then compatibility tab. Check the
compatibility box (run in Windows XP service pack3) and also the "run
program as administrator" box and then OK. I did this about 4 hours ago
and I have not had one single problem. I will wait a few days to be
absolutely certain. I will be also trying it with Protel 99SE which is
also flaky under Windows 7.
Thanks
Peter
>> From: Peter Grey
>> Can you tell me where you make these changes?
>> Thanks
> Hi Peter,
>
> 1. If you are not the administrator, first open Windows Explorer, browse to
> "C:\Windows\explorer.exe", rightclick, "Run as administrator".
>
> 2. In that Windows explorer, browse to “C:\Program Files\”,
> right click on that directory, select Properties, select Security, select
> "Users", click Edit, select "Users", enable the "Write" tickbox and click
> OK. If you are asked if it should apply to all subfolders too, select Yes.
>
> I remember changing the permissions for all in "Program files" but cannot
> reproduce that right now in Win7. The properties of the separate program
> directories however are editable, and that is where the offending program
> tries to write its INI files etc.
>
> Regards,
> Arie de Muynck
>
>> Peter,
>>
>> I’ve had similar problems with Win7 running older SW. Apparently some try
>> to
>> (need to) write in the “C:\Program Files” directory which is not allowed
>> by
>> UAC.
>> Since I consider Windows unsafe anyway, I just changed permissions for
>> that
>> and underlying directories to “R/W for Everyone” and most problems
>> disappeared.
>
Reply by ●August 15, 20122012-08-15
Us Dinosaurs!! I also had major issues with Protel 98. Frankly it does
everything I need, and I see no reason to spend anything on a newer
program if I don't have to just for the sake of it. But I was never sure
whether it was Protel or IAR that caused Win 7 to trash itself. It
basically was unable to recognise any of its own apps, even calculator,
and Notepad were simply not there according to Win 7, yet they had been
until i tried installing my own programs.
I see absolutely nothing to like about Win 7, and lots to dislike, so,
like my old DOS 6.22 machine which lived to a very ripe old age, and
served me well, I'll probably keep running XP until I can't anymore.
Al
On 15/08/2012 3:43 PM, Peter Grey wrote:
> On 15/08/2012 2:01 PM, Arie de Muynck wrote:
> Firstly, thanks to all who replied. I went out to purchase a computer
> and to load Windows XP. When I explained what I intended he suggested
> that I change the properties on the IAR program. I right-click on the
> IAR icon, select properties and then compatibility tab. Check the
> compatibility box (run in Windows XP service pack3) and also the "run
> program as administrator" box and then OK. I did this about 4 hours ago
> and I have not had one single problem. I will wait a few days to be
> absolutely certain. I will be also trying it with Protel 99SE which is
> also flaky under Windows 7.
>
> Thanks
>
> Peter
>>> From: Peter Grey
>>> Can you tell me where you make these changes?
>>> Thanks
>> Hi Peter,
>>
>> 1. If you are not the administrator, first open Windows Explorer, browse to
>> "C:\Windows\explorer.exe", rightclick, "Run as administrator".
>>
>> 2. In that Windows explorer, browse to “C:\Program Files\”,
>> right click on that directory, select Properties, select Security, select
>> "Users", click Edit, select "Users", enable the "Write" tickbox and click
>> OK. If you are asked if it should apply to all subfolders too, select Yes.
>>
>> I remember changing the permissions for all in "Program files" but cannot
>> reproduce that right now in Win7. The properties of the separate program
>> directories however are editable, and that is where the offending program
>> tries to write its INI files etc.
>>
>> Regards,
>> Arie de Muynck
>>
>>> Peter,
>>>
>>> I’ve had similar problems with Win7 running older SW. Apparently some try
>>> to
>>> (need to) write in the “C:\Program Files” directory which is not allowed
>>> by
>>> UAC.
>>> Since I consider Windows unsafe anyway, I just changed permissions for
>>> that
>>> and underlying directories to “R/W for Everyone” and most problems
>>> disappeared.
>>
>>
everything I need, and I see no reason to spend anything on a newer
program if I don't have to just for the sake of it. But I was never sure
whether it was Protel or IAR that caused Win 7 to trash itself. It
basically was unable to recognise any of its own apps, even calculator,
and Notepad were simply not there according to Win 7, yet they had been
until i tried installing my own programs.
I see absolutely nothing to like about Win 7, and lots to dislike, so,
like my old DOS 6.22 machine which lived to a very ripe old age, and
served me well, I'll probably keep running XP until I can't anymore.
Al
On 15/08/2012 3:43 PM, Peter Grey wrote:
> On 15/08/2012 2:01 PM, Arie de Muynck wrote:
> Firstly, thanks to all who replied. I went out to purchase a computer
> and to load Windows XP. When I explained what I intended he suggested
> that I change the properties on the IAR program. I right-click on the
> IAR icon, select properties and then compatibility tab. Check the
> compatibility box (run in Windows XP service pack3) and also the "run
> program as administrator" box and then OK. I did this about 4 hours ago
> and I have not had one single problem. I will wait a few days to be
> absolutely certain. I will be also trying it with Protel 99SE which is
> also flaky under Windows 7.
>
> Thanks
>
> Peter
>>> From: Peter Grey
>>> Can you tell me where you make these changes?
>>> Thanks
>> Hi Peter,
>>
>> 1. If you are not the administrator, first open Windows Explorer, browse to
>> "C:\Windows\explorer.exe", rightclick, "Run as administrator".
>>
>> 2. In that Windows explorer, browse to “C:\Program Files\”,
>> right click on that directory, select Properties, select Security, select
>> "Users", click Edit, select "Users", enable the "Write" tickbox and click
>> OK. If you are asked if it should apply to all subfolders too, select Yes.
>>
>> I remember changing the permissions for all in "Program files" but cannot
>> reproduce that right now in Win7. The properties of the separate program
>> directories however are editable, and that is where the offending program
>> tries to write its INI files etc.
>>
>> Regards,
>> Arie de Muynck
>>
>>> Peter,
>>>
>>> I’ve had similar problems with Win7 running older SW. Apparently some try
>>> to
>>> (need to) write in the “C:\Program Files” directory which is not allowed
>>> by
>>> UAC.
>>> Since I consider Windows unsafe anyway, I just changed permissions for
>>> that
>>> and underlying directories to “R/W for Everyone” and most problems
>>> disappeared.
>>
>>
