zen69x

Simple answer NO You can upgrade to 2000 Server or 2003 Server. You can't go from a server class OS to a workstation class OS.

Sure, to remove that key, you will first have to give yourself full control of that key. By default only system has full control over that key, admins have read only access.

If you haven't gone ahead with this yet, check this out this MS article: http://support.microsoft.com/default.aspx?scid=kb;EN-US;289876

Some scanners provide software to act as a scanner server and allow you to do what you want. Check the manufacturer's website and see if you can't find something there.

Everything you have showing there as high or above normal are processes that belong to the OS. So, unless you want a less responsive OS, leave them alone.

try ipconfig /dnsflush on the machines and see if you can ping them by name and if they resolve to the correct IP then.

This has been available since NT4. I have had mixed results when using this though. Some programs act really weird when you do this, if at all. But there are still some instances where it might be handy.

as far as 2003 server RD on XP, I think someone sells a solution to do this. I've noticed that in XP, the product suite key does not read terminal server, not sure if that has anything to do w/ the 1 connection limitation however. As for the licensing issue, it will come up and say this when you try to edit the product suite key manually, however when you use the install method, Microsoft is nice enough to do this for you, does that still count?

If anyone is interested, I can send directions in e-mail as I will need to attach a file or two. If your e-mail isn't in your profile, please post it or send it to me and I will forward them to you. The whole list is a bit much to post here.

You need to generate accouts on the server that match the account names listed on the clients. Then you will need to assign NTFS permissions to the shares that you want them to have access. If the passwords match on the server and clients, you will be able to just browse to the share. If they do not, you will be prompted for username / password combination.

I would seriously doubt that you'd find USB 2.0 drivers for NT 4. USB 1.1 would be enough to run those peripherals that you'd mentioned and if you could get some solid drivers for USB 1.1 I'd say go with that. As for upgrading. I've no idea what the performance is like under a Cyrix processor. I've seen Win2k on an AMD K6-2 366 with 192MB of RAM and can't say that I was extremely disappointed. Depends on what you want to do with the PC. For web browsing, and office work it'd probably be ok. Actually, as a web browsing PC, I have Win2k installed on a P200 w/ 96MB of RAM and it browses the web and does MS Word and Excel just fine. And I'm typing this on a PII 366 w/ 224MB (laptop's have strange RAM configurations) running WinXP and have to say I'm pretty happy with the performance I'm getting from it.

Open the printer folder then click on file - server properties. From there go to the advanced tab on the window that comes up. You will see the current path of the spooler folder and can change that as you'd like.

well, depending on if you have XP or 2k, I would assume 2k as there is a graphical way to get at the boot.ini in XP. Nonetheless, in either OS, go to folder options, on the view tab, uncheck hide protected operating system files and it should now be visible. (It also might be read only so you will have to uncheck that on the file first.)

This drove me nuts for a long time. If you show hidden files you will see a file called desktop.ini. If you open this you will see the name of the owner and another setting called PersonalizedName. When you are logged in with the owner account it will show the personalized name, otherwise it will say owner's documents. Hopefully this helps.

I had an issue with my scanner working under 2003 as well. Two things to check. First, under services, make sure that the Windows Image Aquisition service is started and set to automatic. If it still fails, check to see if the camera and scanners wizard in the control panel detects it. The second issue I had which drove me mad for quite a while, was that no matter what I did, I could only get it to work with the windows wizards and not with a twain32 interface. The source of the problem? Terminal Services was installed on the PC. If you have that installed, uninstall it. You can still make two administrative connections via remote desktop without Terminal Services installed and my scanner works with the twain interface now too. Hope this helps.

Then go ahead and turn it off. Get TweakUI from the power toys and under explorer, disable the manipulate connected files as a unit option.

in reply to above. Yes Win2k server supports RDP, remote desktop protocol. However, you can't install terminal services under Win2k Pro. The client works fine on it, but there is no option to make it the server end for terminal services / remote desktop.

Quote: After a year of testing the 2 configurations on my rig, XP seemed to not leak memory AS BAD as 2000 did when using Adobe Premiere This then would be a problem with the app, not the OS. Quote: <Windows 2K> Has less fluff/bloatware Doesn't require activation Boots a tad slower Is relatively as fast as XP SP1 Still has DOS support Is getting old (almost 5 years now) Emphasis mine. There is no DOS in Win2k it is based on NT 4 which also had no DOS in it. XP is based off Win2k. There is a NTVDM (NT Virtual DOS machine) included with the OS, same as NT before it and XP after it. The XP VDM has a few extras included as to support sound emulation, you can use VDMSound on 2k or XP if you'd like though.

What was said above is correct. There is no RDP server for Win2k pro. What was said above regarding MS and an ActiveX control is true as well. What it does however, is allow a PC running IIS to host a website that when accessed will allow you to download an ActiveX control in place of using the fullblown Remote Desktop client. The web page allows you to point to a remote desktop server but it does not allow or prevent that PC hosting the site from becoming a remote desktop server. Hopefully that is somewhat clear.

A NIC is not a modem in any sense of the word. A modem's purpose is to change the data it receives in order to transmit it over another medium and to take the data it receives and reconstitute it to its original state. A NIC speaks only one "language", be it Ethernet, Token Ring, etc. Your cable and/or DSL modem serve to take the information off the cable or phoneline and convert it to, in most cases, an ethernet format. As mentioned above, your USB adapter acts as a NIC in this case through the drivers you installed on the PC for it. The issue with the USB scenario is that you can only connect one PC in this manner due to limitations in USB. Using a SOHO router, you can connect multiple PC's via ethernet connections to share a single connection. Hope I was at least somewhat clear on this.

Having all those devices on 1 IRQ under Win2k is by design for the ACPI model. It will work correctly provided the following: Motherboard has a proper implemenation of ACPI Device manager shows ACPI PC under computer PCI cards and drivers are designed according to the PCI 2.1(?) or better spec. Bottom line, if you can't change your IRQ assignments, then it looks like you probably meet criteria #2. You could try removing cards and placing them back in one at a time to see if there is a problem device.

Sorry for the delay. I will post what I changed to get my Adaptec 2930U2 SCSI controller recognized during the install without having to use a floppy. I would imagine that the changes required for your device should be pretty similar. First, what you will want to use the makecab utility found in the \winnt\system32 directory to make cab files of your .sys (driver) and .inf (setup) files. Mine were 2930U2.sys and 2930U2.inf which in turn became 2930U2.sy_ and 2930U2.in_ respectively. You will need to copy these files to the i386 directory that will be burned on your CD. There are only 2 files that you will have to edit: DOSNET.INF and TXTSETUP.SIF Under DOSNET.INF I made the following changes: [FloppyFiles.2] I added: d1,2930U2.sys [strings] I added: 2930U2 = "Adaptec 2930U2 Ultra2 PCI SCSI Controller" [Files] (Be careful, there are two sections labeled this, you want the 2nd, it also has a very long list after it.) I added: d1,2930U2.sys Under TXTSETUP.SIF I made the following changes: [sourceDisksFiles] I added: 2930U2.inf = 1,,,,,,,20,0,0 2930U2.sys = 1,,,,,,3_,4,1 [HardwareIdsDatabase] I added: PCI\VEN_9005&DEV_0011&SUBSYS_01819005 = "2930U2" [sCSI.Load] I added: 2930U2 = 2930U2.sys,4 [sCSI] I added: 2930U2 = "Adaptec 2930U2 Ultra2 PCI SCSI Controller" The stuff in quotes is just a text string so nothing special there that I can tell. The only item I see that would be a problem is the PCI\Ven... etc. part. I got the value by opening the registry on a box that already had the adapter installed and went to the HKLM\System\ControlSet001\Enum\PCI key and searched through the values until I found the key that had the adapter that I was looking for. Alternately, there was a similar setting in the .inf file that is provided with your hardware, I'm not sure if that would work, but I'd bet that it probably would. Mine showed PCI\VEN_9005&DEV_0011 vs. what I entered above. I hope that helps, or at least gives you a headstart on it. If you want some more help, post your .inf and .sys files or link to the download from the manufacturer and I would be glad to take a look with you.

You can do this. I will see if I can post some better information later. I integrated some OEM SCSI drivers onto a CD and now it recognizes the controller during install. No floppy needed.

^^ yup. what skp said.

well, just thought I would throw in my .02. Last known good will not work cuz NT boots fine and to NT, nothing is wrong. NT 4 does support Plug & Play, but only in a very limited way. (I think mostly ISA based cards or something, I would have to look it up) I have seen this once before, usually I would just boot in VGA mode, set the resolution (more like confirm) to 640x480 and hit apply, upon rebooting the problem usually is fixed. However, once time that did not work. What I had the user do was wait for the HDD to stop grinding away after booting, (make sure everything loaded), log into NT. Then while I was looking at another machine, walked them through, using only keyboard commands, getting to the resolution, moving it back to 640x480 and hitting apply. This worked. If you have access to another NT box that is fairly close, try that.