>Well if it runs under Win95 doesn't guarantee that it will work with Win98.
>Win95 has a mixed 16 and 32-bit kernel and win98 has true 32-bit kernel so there are differences. To correct myself Win95 runs all 32-bit programs in system virtual machine and each 16-bit program in separate virtual machines, win98 runs everything in the system virtual machine and this can cause problems with 16-bit programs. Try apply the latest service pack or the newest upgrade, it will fix some problems with 16-bit programs.
>
The core of the Win98 kernel is still derived in part from the DOS environment,and in fact there is a version of DOS underlying Win98. NT, OTOH, is a true 32 bit kernel.
Your statement about where Win98 runs its apps is also completely wrong. Each DOS app runs in its own VDM. Each 32 bit app runs in its own virtual machine as well. All Win16 apps run in a single VDM, which essentially hosts a copy of Win3.x. Unlike NT, you do not have the option of isolating each Win16 application in its own environment; in essense, there is a single shared Win16 environment running.
While more of the guts of Win98 have become a true 32 bit environment, it's far from a complete 32 bit kernel. Issues of DOS and Win16 compatibility are the major reasons that the Win9x and WinNT product paths haven't merged, and we're probably looking at one more major Win9x family release (Millenium) that won't be fully 32 bit.
I'm not familiar with OneWrite, but if it's a DOS application, there are severla things that may need to be adjusted in the .PIF associated with the application. You have the option of either running in DOS compatibility mode, which essentially unloads Win98 while the DOS app is running - no other processes run while in MS-DOS compatibility mode. In addition, there is the option to hide the Windows environment from the DOS application the Advanced button on the Program tab brings up the DOS mode settings page), a less radical step, and there are settings in the Memory to make different types of memory available to the VDM, and to isolate the conventional memory of the VDM from other applications (the Memory tab offers settings for conventional, XMS, EMS and DPMI.)
