Thanks for the info! :-)
You may want to talk to your reps who are going to conferences, and the ones
who produce the marketing materials, since they do make different claims....
it is good to know that the product works that way, in any case.
----- Original Message -----
From: "Ted Peck" <Ted@basistech.com>
To: "Unicode List" <email@example.com>
Cc: "'Michael (michka) Kaplan'" <firstname.lastname@example.org>
Sent: Friday, October 13, 2000 9:32 AM
Subject: RE: A binary that runs on Win9X and WinNT
> Pardon the delay in my response but I'm new to this list - I just joined
> because one of our customers drew my attention to your discussion of
> I'd like to point out that Michka's message below about how our Cheops
> product works is not entirely accurate.
> Here's my clarification:
> Cheops enables a single Unicode executable to run on Win9x and NT/2K.
> has no per-API call runtime overhead on NT/2K, because it works by
> redirecting at initialization time every reference to a Wide API function.
> When running on NT these references are connected directly to the
> system-supplied entry points. Only on 9x does Cheops connect those
> references to Cheops-supplied transcoder functions.
> -----Original Message-----
> 10/11/2000 04:47 PM
> From: "Michael (michka) Kaplan" <email@example.com>
> To: "Unicode List" <firstname.lastname@example.org>
> Subject: Re: A binary that runs on Win9X and WinNT
> I would sooner rip my lungs out then speak ill of a much needed
> but one drawback to Cheops is that *all* Unicode Win32 API calls go
> Cheops, even when you are running on NT4 or Windows 2000. At least that
> true in the version they were promoting at the last Unicode conference.
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:21:14 EDT