DOS/Command Prompt Issue

Crash Override

Ok, more or less, the problem is that a while back I did a computer science course and during it, we were asked to compile something (I think it could have been Java but I'm not sure) using Command prompt.

This involded using CD or Change Directory it was really annoying and it kinda all went wrong (It didnt work for anyone) but the problem now is I can't get back to the path the the DOS was originally on so commands like 'ipconfig' and 'tracert' don't work.

When I type in commands like the one's above I get the following error message in a pop up box..."The ordinal 1001 could not be located in the dynamic link library WSOCK32.dll.

My current path setting is E:\ Documents and Settings\Administrator

I believe the original path was C:\WIN system 32 or something along those lines but I'm not sure.

So, Anyone know what's wrong here?

Any help is most appreciated

Spear

Crash Override wrote: »

Ok, more or less, the problem is that a while back I did a computer science course and during it, we were asked to compile something (I think it could have been Java but I'm not sure) using Command prompt.

This involded using CD or Change Directory it was really annoying and it kinda all went wrong (It didnt work for anyone) but the problem now is I can't get back to the path the the DOS was originally on so commands like 'ipconfig' and 'tracert' don't work.

When I type in commands like the one's above I get the following error message in a pop up box..."The ordinal 1001 could not be located in the dynamic link library WSOCK32.dll.

My current path setting is E:\ Documents and Settings\Administrator

I believe the original path was C:\WIN system 32 or something along those lines but I'm not sure.

So, Anyone know what's wrong here?

Any help is most appreciated

You mean the PATH environment variable? You can set that manually with SET PATH=c:\.....;d:\...;blah;blah;

Otherwise, right click My Computer, choose the advanced tab, and there's an environment variables button there.

Crash Override

Spear wrote: »

You mean the PATH environment variable? You can set that manually with SET PATH=c:\.....;d:\...;blah;blah;

Otherwise, right click My Computer, choose the advanced tab, and there's an environment variables button there.

I tried using the both SET PATH and the eviornment variables window in My computer and I tried many different variables, maybe I'm doing it wong? I'm not even sure what variable/path I have to change it to.

Spear

Crash Override wrote: »

I tried using the both SET PATH and the eviornment variables window in My computer and I tried many different variables, maybe I'm doing it wong? I'm not even sure what variable/path I have to change it to.

The usual is something like

%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;

Crash Override

Spear wrote: »

The usual is something like

%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;

It didn't work either, Should I be using the user variables for administrator or the system variables?

It might be significant to mention that I'm running on Windows 2000 on this machine.

Maybe I should try suing CD? (Change directory) because SETH PATH doesn't seem to work, thing is I dont know what Path I should put it to.

Spear

Crash Override wrote: »

It didn't work either, Should I be using the user variables for administrator or the system variables?

It might be significant to mention that I'm running on Windows 2000 on this machine.

Maybe I should try suing CD? (Change directory) because SETH PATH doesn't seem to work, thing is I dont know what Path I should put it to.

PATH is a system wide variable, it bears no connection to your current directory.

You should be setting it as a system variable. The contents of the user variable PATH are simply appended to the system variable.

JimmyL

PATH is probably not the problem. Well not directly. You have more than one version of WSOCK32.dll and the commands are picking up the wrong one. The bad one is likely to be in "E:\Documents and Settings\Administrator" or somewhere on your PATH. The correct one is (probably) in "C:\Windows\System32". Assuming C:\Windows is where Windows is installed. Since, the commands worked in that directory/folder.

Captain Furball

Your java install messed up your environment variables.
Check to see are you missing a ; in the PATH, there used to separate directories.


And since your programming all whats happening is your java needs to access an external function inside the dll so it uses the ordinal to look it up. It's kinda of like using an offset.
Hope ya figure it out.