>Hi Jon,
>
>> Forgotten about that. I guess I should bite that bullet.
>> Maybe I will get lucky and someone on this list will jump in and say that
>> they also have tried it and will post results about 64-bit Win7 and that
>> and save me time!! I can hope.
>>
>> That said, do YOU have problems on Win7 64-bit, Paul? I mean, if it is in
>> the DLLs and you use them.... then you should know about it, yes? That
>> would close the door. But if you are NOT having problems you can assign to
>> the DLL and Win7 64-bit, then perhaps that is a strong indicator in the
>> other direction -- IAR, instead.
>
>There are issues. When TI introduces a new device family, with a different
>set of JTAG/SBW bugs, the DLL needs changing and potentially the firmware on
>the device.
>
>> > However, there is a 3P mailing list for the DLL and tools and some 3Ps
>> > have a rant now and again.
>>
>> Are you talking about point-to-point??? Like I once thought to replace
>> what I did use, which was SLIP? That PPP? The one where all the packets
>> must be delivered in order?
>
>No, 3P = third-party.
>
>> Who is doing that for mail, today? How do I connect in?
>
>Unfortunately, you can't until you sign a TI NDA.
> Most of the machines we have at my company are still
XP. But Win7 seems
> to work fairly well for most people. There are some things that Win7 does
> better than XP (such as making better use of larger memories and multiple
> cores on newer machines), other things it does worse (such as hiding what
> it is doing with program files and directories, leading to these
> compatibility issues). Overall, I don't see it as much of a win or a
> lose. I'll stick to XP on my old windows machine - but when it
retires,
> it will probably be replaced with Win7.
>
> But most of my work these days is done on Linux - either directly on
> Linux, or within a VirtualBox machine hosted on it. I've had very few
> problems using XP in VirtualBox machines. I have not used IAR's
tools,
> but I have used a couple of versions of Code Composter for the msp430
> within VirtualBox machines, and that has all gone smoothly - including
> debugging over USB.
Personally, I use a MacBook with OS X and if I need Windows then I run
Parallels. I have a Windows 7 VM and a Windows XP VM on the MacBook. I run
Visual Studio 2008 on Win 7 and some other legacy stuff that doesn't work
on Win 7 (driver issues) on XP all under Parallels. Works a treat--no need for
three laptops.
At the office I have a Win7 x64 machine with gobs of memory and an SSD for main
development, but I don't honestly see that many problems with Win 7 when
developing.
> Forgotten about that. I guess I should bite that
bullet.
> Maybe I will get lucky and someone on this list will jump in and say that
> they also have tried it and will post results about 64-bit Win7 and that
> and save me time!! I can hope.
>
> That said, do YOU have problems on Win7 64-bit, Paul? I mean, if it is in
> the DLLs and you use them.... then you should know about it, yes? That
> would close the door. But if you are NOT having problems you can assign to
> the DLL and Win7 64-bit, then perhaps that is a strong indicator in the
> other direction -- IAR, instead.
There are issues. When TI introduces a new device family, with a different
set of JTAG/SBW bugs, the DLL needs changing and potentially the firmware on
the device.
> > However, there is a 3P mailing list for the DLL and
tools and some 3Ps
> > have a rant now and again.
>
> Are you talking about point-to-point??? Like I once thought to replace
> what I did use, which was SLIP? That PPP? The one where all the packets
> must be delivered in order?
No, 3P = third-party.
> Who is doing that for mail, today? How do I connect
in?
On 15/08/2012 08:39, Onestone wrote: > 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
Most of the machines we have at my company are still XP. But Win7 seems
to work fairly well for most people. There are some things that Win7
does better than XP (such as making better use of larger memories and
multiple cores on newer machines), other things it does worse (such as
hiding what it is doing with program files and directories, leading to
these compatibility issues). Overall, I don't see it as much of a win
or a lose. I'll stick to XP on my old windows machine - but when it
retires, it will probably be replaced with Win7.
But most of my work these days is done on Linux - either directly on
Linux, or within a VirtualBox machine hosted on it. I've had very few
problems using XP in VirtualBox machines. I have not used IAR's tools,
but I have used a couple of versions of Code Composter for the msp430
within VirtualBox machines, and that has all gone smoothly - including
debugging over USB.
Reply by Onestone●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.
>>
>>
Reply by Peter Grey●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.
>
Reply by Arie de Muynck●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.
Reply by Matthias Weingart●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
Reply by Jon Kirwan●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
Reply by Jon Kirwan●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.
