I_Broke_My_MHZ

Where are the installation files located?

I doubt it's a problem with ZoneAlarm. The program aparently just generates its own log when something crashes. From the look of the error, a symbol in ntdll.dll is missing. Maybe that file got messed up?

Allowing them on the clients is OK in theory as long as you maintain the policy of keeping up to date with patches, but in practice it isn't a good idea because users generaly cannot remain responsible with such tools. Having them on the server themself? Are you kidding me? That is a definate NO.

I remember that if you press F8 before starting windows and then choose selective startup, you can set windows to load everything but what you want. The last question it asks is if you want to load the GUI.

Oh, well then maybe there is a problem with the hard drive. The BIOS should tell you that there is something wrong. I guess the computer must not have SMART technology for whatever reason. I suggest booting with a floppy, preferably a Win98 floppy, and see if you can run fdisk and change it to fat32. If fdisk can't access a disk at all then the hard drive is definately busted.

I breifly gleaned the error logs. It would appear that it is unable to connect to the remote server due to problems with the RPC server.

I think you may have downloaded the 64bit version of WMP by accident.

Doesn't sound like a hard drive problem. The data was probably corrupted. Boot into the recovery console and run chkdsk.

Try holding the button for a good half a second.

Do you have trouble configuring the server to allow it or the clients to connect to the share? Can you give more info on what version of DOS you have on them, and any other programs?

This might help. http://support.microsoft.com/default.aspx?...b;en-us;Q224370

Maybe it is just me, but I don't see the image.

Describe exactly what happens when you try to shutdown windows. Do you close all programs prior to shutting down windows or what is left on when you shutdown?

Boot into safe mode, or keep trying till you can get it to succssfully start up, then go into administrator tools > event viewer and take a look at the errors. I think explorer.exe might be having problems starting properly.

You can't wait until you get a new version of a browser? You want it that bad? It's a browser, get over it.

As long as nLite removes it....

A desktop that is managed by the NT4 server, that's going to be something that you have to let someone else worry about. I don't know much about NT4 server, but I think it's a safe bet that the task is much harder in that dated OS. Securing the computers requires a group policy, which is managed by the server. You will probably have to manually set one up on each of the computers because since NT4 is so old, it doesn't have all the options you should have to set the policy. Man that old server is gunna give you a lot of fun. Upgrade all the computers to XP pro but keep NT4 on the server, your council is probably just a bunch of idiots who decided they wanted to use XP at work.

A logical assumption except I already did a memtest and passed. Additionally, I learned later, a program can't assign a value to the memory address 0x00000000 anyway because it's part of the protected memory address range. So memory wasn't the problem. I did figure out what it was: the printer. For some reason Office 2000 has this quirk where it will crash if the default printer is a network printer and not connected. Before I had this problem back in the days of Windows 2000, but last time it reported an error with a library (which turned out to be a HP printer library, so I was easy able to resolve the problem). I had it set to a network printer by default (a big no no I guess) and instead of the nice error with a .dll I get a mysterious memory error. But I fixed the problem, just added a new non-network printer and set that to default. I guess I threw you off with the upgrading the memory part. I upgraded the memory around the time I changed the printer configuration.

I recently upgraded from 512MB to 1.2GB of memory. Ever since then I have been getting "the memory could not be "read" errors. I suspect that there might be a problem with the chip itself but the memory test (memtest86) I did revealed nothing. The error always appears like this: The instruction (first address) referenced memory at (second address). The memory could not be "read". Click on OK to terminate the program These are the programs, first and second memory address that were referenced in the last four errors I got: winword.exe 0x6061fdc3 0x00000000 firefox.exe 0x6061fdc3 0x00000000 winword.exe 0x6061fdc3 0x00000000 winword.exe 0x6061fdc3 0x00000000 rainlender.exe 0x6061fdc3 0x00000000 As you can see, there is a distinct pattern. What could be the problem? What can I do to fix it?

It gets a bit complicated, but it will be easy once you get it setup. First download and install YnHub (search for it). This is software which you can create your own hub with. Once installed and setup properly, run it and load DC++. In DC++ create a new favorite hub with the hub address of 127.0.0.1 and you will connect to your own hub. Everyone else connecting to your hub must know your IP address to do so. I'm not sure how it works for your Uni network exactly, but this will probably work. Find your IP address by using ipconfig, then have everyone else use that as the hub address. Make sure you have active mode setup properly.

Making that conclusion about Windows 98's memory management based on those programs is kinda foolish. Those memory "optimizers" do not work, they only mislead. A lot just make things worse by "optimizing" your memory.

Token ring would be pretty much useless and inefficient due to the very low speeds and ancient technology.

You're using windows 2000? Do you think I'm a mind reader? I didn't know that.

Two wrongs don't make a right!

Billions of dollars to create the first, $40 for every one after it.