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.
Problems with IAR Kickstart
Started by ●July 18, 2012
Reply by ●August 15, 20122012-08-15
Reply by ●August 15, 20122012-08-15
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.
--
Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
SolderCore Development Platform http://www.soldercore.com
> 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.
--
Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
SolderCore Development Platform http://www.soldercore.com
Reply by ●August 15, 20122012-08-15
> 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.
--
Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
SolderCore Development Platform http://www.soldercore.com
> 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.
--
Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
SolderCore Development Platform http://www.soldercore.com
Reply by ●August 15, 20122012-08-15
On Wed, 15 Aug 2012 08:52:39 +0100, you wrote:
>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.
Ah. Explained. Thanks.
Jon
>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.
Ah. Explained. Thanks.
Jon
