I've worked on similar UNIX->NT porting projects. Filenames really suck on NT.
1. There is two names for non 8.3 filenames
2. The default location for installation of Vendor software is "%SystemDrive%\Program Files". This is a pain in the ass for command line utilities that take absolute pathnames as parameters.
Various other things are a pain in the ass like password authentication, user creation/deletion in a domain environment, temp file creation (%TEMP% is a user environment variable not available for services). I can't remember anything offhand that was better on NT except the product installation. With InstallShield for UNIX, I don't think this is the case any more.
i don't like to gripe, but i suggested this story to cnn over a year ago and they're only airing it tonight. do they even listen to the public? it's not like they get many suggestions for stories, right?! jeez.
Intel PCs running Windows are typically single use machines so CPU ID maps to a user. Sun workstations are frequently multi-user and users frequently use more than one machine so mapping the CPU or hostid to a user would be silly.
Rob, Any chance of updating the source?
Thanks,
Sean
I've worked on similar UNIX->NT porting projects. Filenames really suck on NT.
1. There is two names for non 8.3 filenames
2. The default location for installation of Vendor software is "%SystemDrive%\Program Files". This is a pain in the ass for command line utilities that take absolute pathnames as parameters.
Various other things are a pain in the ass like password authentication, user creation/deletion in a domain environment, temp file creation (%TEMP% is a user environment variable not available for services). I can't remember anything offhand that was better on NT except the product installation. With InstallShield for UNIX, I don't think this is the case any more.
To summarize: UNIX is great.
i don't like to gripe, but i suggested this story to cnn over a year ago and they're only airing it tonight. do they even listen to the public? it's not like they get many suggestions for stories, right?! jeez.
Intel PCs running Windows are typically single use machines so CPU ID maps to a user. Sun workstations are frequently multi-user and users frequently use more than one machine so mapping the CPU or hostid to a user would be silly.
Pretty useful for Intel to track stolen chip too!