 |
|
List Archives >
Mathcad List Archive >
Archive by date >
This Month By Date >
This Month By Topic
[mathcad] Re: Mathcad 13 and MBR corruption?
| [mathcad] Re: Mathcad 13 and MBR corruption? |
|
Author: Gray, Steven G
Posted: Mon, 10 Apr 2006 10:09:41 -0400
|
I like the marine boot idea better, though a public flogging is also
high on my list. Software companies that insist on vile copy protection
schemes deserve to fail- and ultimately will whether they deserve it or
not. The right answer is to eliminate it, not debug it.
Steven Gray
Lockheed Martin Radar Engineering
From: Pergande, Albert N
Sent: Monday, April 10, 2006 9:26 AM
To: Mathcad Discussion List
Subject: [mathcad] Re: Mathcad 13 and MBR corruption?
Better idea - make him debug it.
Al Pergande
Senior Radar Engineer
Lockheed Martin Missiles and Fire Control MP 200 5600 Sandlake Road
Orlando, Fl 32819
Voice 407-356-5169
Fax 407-356-0933
"albert.n.pergande"
for personal mail - "al"
From: Aldo P. Solari "mailto:aldo.p.solari"
Sent: Monday, April 10, 2006 7:02 AM
To: Mathcad Discussion List
Subject: [mathcad] Re: Mathcad 13 and MBR corruption?
Jesper, you may be right on that most Windows related problems are to be
blamed to MSoft. True.
HOWEVER, the C_Dilla thing (and all the problems, production stops,
etc. it implies) is *solely* due to MathSoft. In the long run, this
issue may come to cost the life of the package, so to say.
The MathSoft CEO who decided to incorporate C_Dilla deserves ... let me
see: a big kick in the butt with a large US Army boot - no, wait, not an
Army but a Marine boot :P
Cheers!
W/best wishes,
Aldo P. Solari (fisheries biologist)
"asolari" (academic matters)
"aldo.p.solari" (private matters)
Home: www.ulpgc.es/webs/ffresearch-solaris
(U. of) Las Palmas, Canary Islands [10/04/2006, 11:54 GMT]
Original message:
"jgu" wrote [08/04/2006, 15:30]:
GJ> Dear Mark
GJ> Before you blame mathsoft, you should consider, whether another
GJ> culprit could be to blame, ie Microsoft, by not making the
GJ> crucial details of the operating system completely transparent,
GJ> and by not being fully backwards compatible, and by cripling
GJ> well-functioning software each time the windows system is
GJ> updated. Effectively, Microsoft may be to blame for cripling
GJ> really innovative software developpers as Mathsoft.
GJ> It's hard to prove, but those of us who have a long experience can't
GJ> help to suspect, that is what is going on. Each time I get a new
GJ> patch for windows, there is a risk that well-functioning software
GJ> suddenly stops working, . I continue to use Mathcad, it's a
GJ> marveilous product, for research and analysis. But have some times
GJ> to use earlier versions, such as the very efficient version 7
GJ> (allthough I have later versions) for critical applications.
GJ> best regards
GJ> Jesper Gundermann
|
[View Complete Thread]
Previous by date: [mathcad] Re: Mathcad 11 - Wheel Mouse Causes Crash, Mike Austin
Next by date: [mathcad] RE: Mathcad 11 - Wheel Mouse Causes Crash, Jean L J Rosenfeld
Previous thread: [mathcad] RE: Mathcad 11 - Wheel Mouse Causes Crash, Potter, Mick
Next thread: [mathcad] RE: Mathcad 11 - Wheel Mouse Causes Crash, Potter, Mick
|
|
|
RSS Feeds
Packs
