> This is a nasty problem - it seems that Win95 insists on > UNICODE and ignores the "this is ascii" bit, and NT4.0 SP3 > insists on ascii, and ignores the "this is unicode" bit. > > Hmmmmmm. Client specific code maybe ? (Gag.....) can we just throw in ascii->unicode conversions all over the place, and have done with it?