cadsi@ccad.uiowa.edu (CADSI) (06/12/91)
Well, I have downloaded MicroWerk's MicroLink Windows comm program. Just so you know, it is not done. Let me put it this way: PLEASE, PLEASE, PLEASE, if programmers want to develop software for Microsoft Windows Version 3.0 and higher, get the doggone SDK. WHY??? For the DEBUG KERNELS. MicroLink successfully crashes windows before it even starts if as the debug kernels are in place. What does this mean???? MicroLink is doing something nasty, but not really catch'able with the regular run-time version of Windows. this is a pity, 'cause the think looks darn nice (I had to leave Windows, reload the run-time kernels, rerun Windows, then run MicroLink just to see this - get my drift now?). As a side note, WinQVT runs, but when you exit, it crashes the debug kernels. Again, a pity, 'cause this also has good potential as a product. I am certainly not without sin and I commend both companies (the MicroLink folks and WinQVT folks) for trying, but I guarantee you all, if you ever cough up the money for the SDK, you'll anger at programmers who don't and prove it by shipping a botched product. I know I'm not the only guy programming Windows, so others must get angry too. BTW, I don't work for Microsoft, and I use Borland's compiler, and I have stock in neither, this all just makes me grouchy. |----------------------------------------------------------------------------| |Tom Hite | The views expressed by me | |Manager, Product development | are mine, not necessarily | |CADSI (Computer Aided Design Software Inc. | the views of CADSI. | |----------------------------------------------------------------------------|