Subj : Re: cw3220
To   : borland.public.cpp.borlandcpp
From : Sebastian Ledesma
Date : Mon Aug 02 2004 04:26 pm

Glenn:

Borland C++5.0x includes a facility in the IDE to deal with the Windows
targeted version,
Options->Project->Linker->General: Subsystem version 4.0.

Also dont forget to delete the precompiled headers (myproject.CSM) if you
wish to avoid silly phantom bugs when you
switch from a target to another in the Target Expert.

Finally, there is a strange bug around common dialogs. As I rememer If you
have an OWL application , just select File Open (or something that brings
you the standard open/save dialog), press cancel and then close your
application a exception while rise.
The bug is apparently caused by Microsoft DLL that switch some FPU precision
flags (to make code runs faster!?!?!, but with less precision?!?!?!?) , and
can be avoided by calling _fpreset just after the OpenSave Dialog.

Example:
   TFileOpenDialog::TData FilenameData
     (OFN_FILEMUSTEXIST | OFN_PATHMUSTEXIST,
     "Audicom Files (*.mp?;*.wav;*.ecm;*.??0)|*.mp?;*.wav;*.ecm;*.??0|Wave
Files (*.wav)|*.wav|MPEG Files (*.mp?)|*.mp?|Ecam Files
(*.ecm;*.##0)|*.ecm;??0|",
      0, audioDir, 0, 0 /*4096*/);
  if (TFileOpenDialog(this, FilenameData).Execute() != IDOK) {
     chdir(AudicomDir);  //Si cancela no cambia el directorio.
   _fpreset(); //esto lo lei en alguna parte, despues de llamar al Common
Dialog me queda mal la configuracion de punto flotante
   return;
    }
  getcwd(audioDir, sizeof(audioDir));
  _fpreset(); //esto lo lei en alguna parte, despues de llamar al Common
Dialog me queda mal la configuracion de punto flotante


Saludos
Sebastian

"Glenn Jarvis" <gaj@uppergroove.ca> escribió en el mensaje
news:410D871C.902@uppergroove.ca...
> Ed Mulroy [TeamB] wrote:
> > This is a guess.  I do not know if this applies to you.
> >
> > You do not necessarily have a problem in cw3220.dll.  The problem
> > could be caused elsewhere and only appear when code in cw3200.dll is
> > executed.
> >
> > There is a macro named WINVER.  If it is greater than 0x400 then you
> > need to change its value to work with Win98.
> >
> > That macro is used by the Windows header files to control how the
> > structure used by the open/save common dialogs is defined.  If it is
> > greater than 0x400 then the structure is larger.  If you manage to get
> > the program to launch under Win98 then it may generate an error.
> >
> > Try putting these lines before the first include in each source file,
> > build and try it.  It is easy to try and if it does not help, it is
> > easy to remove.
> >
> > #ifdef WINVER
> > #undef WINVER
> > #endif
> >
> > #define WINVER 0x400
> >
> > I hope this helps.
> >
> >
> >>soory for my bad english ;)
> >
> >
> > Do not feel bad about your English.  Your message was very clear.
> >
> > .  Ed
> >
> >
> >>Clems wrote in message
> >>news:40d29e06@newsgroups.borland.com...
> >>
> >>i created one application with bc++5.0 and the application
> >>works good with OS Xp and 2000.
> >>
> >>But If it works with 98, if i click in  "open"  or "save" file, when
> >>i close my application, MessagBox  error appears "name
> >>application" ......error.in cw3220.dll.
> >>
> >>I searched on internet   http://www.instantid.com/support/faqs.asp#2
> >>it's same error but i didn't find any solution for resolve problem
> >>i've got problem with DLL cw3220.
> >>
> >>soory for my bad english ;)
> >>
> >>
> >
> >
> >
> I'm experiencing a similiar problem. I've been working on a application
> for quite some time and originally it was being developed under Win95.
> However, now I'm continuing development on the applications, but under
> Win98SE and the error starts coming up referring to cw3220.dll
> It never happened before under Win95. Anyway, I did some searching and
> supposedly there is a undocumented change between Win95 and Win98 that
> you know who supposedly never publicized. How to get around the problem
> is something I haven't located yet. If I can't find the solution, I may
> be force to convert the entire project over to something else, which
> will truly be a royal pain.
> My point is though, maybe this has something to do with Windows, or
> something else in reference to it's maker?
> Glenn

.