how come (not what the Indian asked the man who said his dick was so long he had to tie it in knots):

NT told you if the domain controller couldn't be contacted but 2K doesn't
2K lists network drives with a red X if you reboot and look in My Computer even if they really are connected
in NT you could map any drive as any user if you could supply the right credentials but in 2K if F$ is mapped by the admin on a given machine, if the admin is logged in as the user and tries to map F$ it will accept the password but then say it can't be mapped because it is mapped by another user on that machine

A

I don't know if NT was better or just different but sometimes the changes from one to the other get me down
like when you press Ctrl-Alt-Delete to lock workstation the key is now 'k' instead of 'w'
mapping a printer in 2K is slow but fast in NT (in 2K my AD won't let me map to a printer even though they are listed so have to map the old way)

in NT if I installed Office as admin on a client machine where drive C: was FAT and then later converted to NTFS when the user logged in they would be prompted every few seconds for the password for drive C: access

in 2K w/ O2K you can't configure Outlook for the client unless you first configure it as admin (haven't done the XP/OXP trip yet)

but my latest 'thrill' concerns the BIOS
I had to take a machine from 2K to NT (don't tell Bill) and found that NT wouldn't run properly
had to go reload BIOS defaults and re-install
same thing when I took one from XP to NT (sorry, Steve)
which leaves 2 questions:

1) why does the OS write to the BIOS
2) what does the OS write to the BIOS

for all I know there are reasons for these thing

A