CompuServe Messages

BRADLEY, NO! You STILL DON'T GET IT!! You do NOT have to do ANY of that! One more time, with feeling: I AM NOT TALKING ABOUT **PORTING** 3DSr"5" TO OS/2!! I am talking about making the WINDOWS NT version (read that again, Bradley: THE WINDOWS NT VERSION!!) capable of running under OS/2, just as most Windows 3.1 and Win32s programs can do RIGHT NOW! IBM is doing all the work to make that happen! ALL AUTODESK HAS TO DO IS MAKE SURE 3DSr"5" DOESN'T USE ANY OF THE NON-SUPPORTED WIN32 API CALLS! And since the ones that aren't supported are mainly stuff that only low-level techie-type utilities would need anyway, that really shouldn't be a problem! There need not be any programmers making a port, since there IS no port. There need not be any more support staff. There need not be any marketing done for the OS/2 version since there IS no OS/2 version (though it wouldn't hurt sales to be able to put in the ads the single line, "Runs under Windows NT 3.51 and OS/2 Warp SMP [or whatever]!"). No need for storage for unsold boxes since it will be the SAME BOX! Do you get it now, Bradley? Has it sunk in yet? Since you brought up OS/2 1.3, I might remind you that the latest Windows NT is only 1.5 at best. They CALL it "3.5" but that's even more bogus than 3DSr"4". There was never a 3.0, or even a 2.0 for that matter. You don't go straight from 1.0 to 3.1. Of course, Microsoft has a history of pulling such shenanigans (Word for Windows 2.0 followed immediately by Word for Windows 5.0, and the latest and greatest example: Access 2.5 is the current version of that product, while the next version will be — Access 7.0!!). Though in another sense, Windows NT really is up to Version 3.5, since NT 1.0 was in reality MS-OS/2 3.0. Which makes Warp actually OS/2 4.0! I will agree with you (and have already) about the relative merits of HPFS vs. NTFS. I will also point out that both are SLOWER than good ol' FAT unless you have at least TWICE the recommended RAM for the OS in question.