Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror

Comment "Developer complete" (Score 1) 387 387

Notwithstanding its clear bugs and usability flaws, Windows 3.0 was the first version to allow developers to fully use the PC's memory and processor. It was the first version I developed for, and I continued to target it for many years after users had moved on to the more stable, polished and complete 3.1 and 3.11 versions. Although, it was a pain to exit to DOS, compile something, launch Windows, execute it, and repeat.

Comment Re:Yeah (Score 1) 348 348

And developers using file access APIs in Windows can get case sensitive behavior. It's just a single FILE_FLAG_POSIX_SEMANTICS flag to CreateFile and friends. It's actually easier to do that in Windows because it doesn't require a reformat and reinstall.

For the record, note that this is no longer true as of Windows XP and later. FILE_FLAG_POSIX_SEMANTICS is overridden by the ObCaseInsensitive registry key, which defaults to 1, meaning that all opens will be case insensitive. See this kb article for example. Changing this requires a reboot, but not a reformat.

"Pok pok pok, P'kok!" -- Superchicken

Working...