Ge0ph

I have a simaler setup, but no VPN. It is set up like a regular nic on a LAN and it works great. It even does internet sharing for my whole family. Does you ISP require VPN? If so, then your setup is different then mine, of not, that could be the problem because that looks like the only difference between yours and mine.

LS120's are a ide device so it is set to either master or slave. I had this happen once a long time ago and if I remember right, the bios of the board I was using at the time would not let me use it as drive a:. So it could be a limitation of your bios?

The only thing I can tell you is that the LS120 on my server is drive a:. That computer never had a real floppy drive so that may be why.

Get some Partition Magic boot disks and just copy the partition to the new drive then set it as master and your up and running. I have done this twice in the last month and it works real smooth.

I use the one with Fix-it. It is Trend drivin.

I have this happen on my server. Everthing else is working fine and has for two months. I have asked several people and they all say the same thing: Who konws?

Not much info here, It's hard to help when you don't let us know what video card and what drivers. Where the drivers digitaly signed by Microsoft? W2k is very stable but some drivers are not. You should place blame on the writers of the drives and not W2k. I don't know if this applys to you but a lot of people will do a "specal hack" of a beta driver to get their hardware to work until offical drivers come out. And when the offical drivers are available they try to update the driver on top of the hacked version. Most of the time it is the hacked part of the old drivers that mess up the driver update and the people get mad because the driver update did not know how to handle the hack. If you have done anything less then "Offical" with your drivers you should clean out all old parts and hacks of a driver before up[censored]. If you have done some hacks to get your drivers to work you should not blame W2k or the new drivers, but instead blame yourself. I have this happen to me, I think I'll just take a chance and update the drivers over my hack. Sometimes it works sometimes it doesn't. But when it doesn't I know it's probably my fault because I'm the one who done something nonstandard.

Like MSGuy says: run "sfc /scannow" , it's the key to a stable W2k system.

If you look at the blue screen dump, sometimes you can pick out what is causing the dump. That's what it's for. Most of the time for me it has been a bad driver. I have not gotten one in W2k (been runningit sence December) but I would get one from time to time in NT4.

OK, this may be right or this may be wrong but here is how I set mine. Reboot my computer and then use it normally for about an hour or so. Then open up the task manager and go to the performance tab. Look at the “Commit Charge” section and see what the peak says. You can lower the size until the peak is a little closer to the limit. The peak is the most you have used in this session. There are no exact numbers to use, you just have to adjust it to your own use. If your peak never gets close to your limit then you can probably get by with out a swap file. If you have a small swap file and your system runs out of memory then just up your swap file I bit. But use the task manager numbers to go by. I have 288 megs of memory and my swap file is set to 16 meg on a separate hard drive. When I play games (UT) I set my swap to 128 just to be safe.

The newest Audiograbber is 1.62 and it can rip with out an ASPI layer in W2k. I use it with LAME encoder and it is better then AudioCatalyst 2.1. www.audiograbber.com

The dump gives you a blues screen with a lot of information on what made your NT/W2k crash. If you find this information usless then you probably shouldnt' care if you can get the dump. On a new machine I like to have the dump until I get the machine running good (no driver problems). Then I adjust the Page file based on info in the task manager after a few hours of normal use. Right now I have 288 megs of memory and a 32meg page file on a seperate hard drive. Ars has a good article about this. http://arstechnica.com/index.html

If you don't like it, just don't use it. But don't post if you don't have question or an answer. Leave us real NT guys alone, we are very happy with W2k. So please crawl back under your bridge and play your little games on your DOS/9x kernal and leave us alone, please. Because you do mean to piss everyone off.

I just bought one yesterday(Offic Max has them for $40). I thought I would have a battle to get it to run but I didn't. I installed the drivers throught device manager and went to the wintv2k dir onn the CD and ran setup, and bang, it worked!!! Maybe I just got lucky.

Well, did you miss the 7 page thread that jdulmage started? It was entertaining. If you missed it, go check it out. http://www.ntcompatible.com/ubb/Forum3/HTML/002104.html

I just ran the makedisk file under W2k and then tried to boot from those disks. Missing NT boot loader. So now I am at a loss.

When I made my boot disks under W2k it put Caldera OpenDos bootup files. Strange? This was with the upgrade that I downloaded, I have not tried it with my actual PM CD but the files look the same. I am going to try it again off of the PM CD and not the download files just to see what happens.

On your Cd, got to the :\english\dos-0s2 dir and run the makedisk file. You can do this from W2k to make PM boot disks. If you only have a W2k machine and you can't install PM then this is how you need to do it. If you have a 9x machine then you can make a boot disk and copy some files off the CD but if you don't have a 9x machine or boot disk then you should run the makedisk utility.

jdulmage: Have you or have you not tried it. In one sentence you say you did it and it works and then you turn around and say you might try some of the suggestions before you delete windows. You say delete the windows dir and msdos.sys but they don't exist on a W2k setup. And yes you can put dos files on a NTFS partition but you can't run dos from a NTFS partition. I can put UNIX fils on a HPFS but you can't run UNIX from it. However, this thread has been one of the most entertaining reads I've done in a long time. I laughed, I cried, well mostly laughed.

First, on my W2k machines there are no Windows dir's or msdos.sys to delete, BECAUSE IT'S NT, not windows 9x. Second, probably what made it work is the reinstall of W2k. A reinstall can do wonders to a messed up machine. Third, and this ones a guess, any DOS files that try to run under any other OS should give an "incorrect version" error.

I have also fond it is good to check for errors before moving/resizing a partition. Partition Magic has a basic error checker that can be disabled. If it does not catch an error or that feature has been disabled you can lose data. A lot of people will disable the error checker because it makes PM run faster and then they swear at PM because it messed up there computer. It's a short cut you don't want to take.

Who cares? Just use what works for you. If you are unhappy with what you are using then try something else. But the bottom line is: Use what works for you. Don't let some one else tell you what is best, make up your own mind. Your the one who is going to be using it, not them.

You can also creat rescue boot disks from the Partition Magic CD under Windows2000. From past experince I have fond it to be safer to do your partitioning from a floppy.

For me every thing works great untill the last step. After I put the HD on the 66 controler Windows will not boot, it just sits there at the last grapical screen. I have tried new drivers but it does not work. Thats why I recomend the Promise card. It works!!!!!

I fought with my BP6 for months and finily got it to work. The solution: Install a Promise Ultra66.