if you can start in safe mode, you could do search and destroy mission for it in the registry (netji.exe) and see if you can find it there, perhaps in hkey local machine/software/microsoft/windows/current version/run and all the run keys. consider exporting registry first to back it up yada yada
you need msconfig.exe. i always get mixed up with which os it comes with. i think with win2k you need to copy it from an xp box. if you had it you could see better from where netji.exe was getting called...
i have had excellent luck with product called 'registry healer' to shotgun patch-up orphan registry entries. about $40 and worth it. swedish i think or slavic...excellent web service. very nicely written utility imho. a gem. haven't used it on win2k but trust the guy that it works based on my experience with it on winME and win98.
ps. you got caught in catch-22 with 'last known configuration' as once you log in, that is considered a good configuration, see, and clobbers last stuff. then there is nothing you can do except find error and nuke it. last good configuration is what you try when you can't get as far as login screen, see? i have yet to have it save me but i know nothing, nothing!!
good job trying booting in safe mode, yes? means it is fixable if we just knew what part of the assembly line to hit with the sledgehammer as we used to say in the motor city...
i wonder if a win2k repair would fix this? is worth a try maybe. i wasn't paying attention to my book that day...i have only used it to fix 'no boot' machines...win2k repair:
boot from win2k installation cd and make like you are going to reinstall. if you have the nerve to invite 2k installer to clobber your current installation, it will instead offer to repair it. this has worked like charm several times i've used it but i've not used it to fix problems like yours, which depending on just how you 'removed' those programs, sounds like an orphan registry entry?...
