Hugh Senior wrote:
[re app hanging on nt]
I'm no NT expert either, but I have been using the NT/MC combination daily
for over a year with no problems. Applications developed under NT have also
worked flawlessly on all client machines (NT, 95, 98) including server
delivery over their networks.
Yes... What I have found with another tool is that apps developed under
NT will work on other Win32, but apps developed on other Win32 will not
necessarily work with NT.
For instance if one is using 16-bit external C code objects, they'll
probably function adequately under 9x, but fail under NT.
And if any part of your code attempts to access hardware directly, NT
will kill it, since that is strictly forbidden in the microkernel
architecture.
Also, as Scott mentioned, securities and permissions are important.
Also, NTFS-formatted drive slices 4 Gb in size might be incorrectly
reporting themselves to your app, causing it to hang up while it tries
to figure out how to run on a drive with something like -2584629593 Mb
available.
A rule of thumb to *always* follow with app development is "port early,
port often". Assuming that just because an app works on one system it
will work on all is a costly mistake. For instance I'd bet you're
looking at a completed app here. Deconstructing it to find the source of
the trouble could take many times longer than it would have done to just
go back and forth as you built, confirming functionality. (Ouch.)
I know that MS claims, more or less, that the Win32 API is consistent
across their 3.75 flavors of it, but Microsoft, inarguably, is staffed
by liars. You can't trust anything they tell you.
I don't know that anyone's going to be able to help you find the
problem... at least not without some more details, such as where the app
is hanging, how "hard" it's hung, system environment ("Win98" is not a
description of a system environment) and so on...
--WthmO
