Jump to content


Setharnas

Member Since 17 Jan 2010
Offline Last Active Private

Posts I've Made

In Topic: Animation-weapon consistency

08 July 2010 - 05:12 AM

It's been a while since I last took a trip to the Underdark, but I think I always associated that animation with the drow halberd-thingie... Unless my memory really plays a trick on me. Would that work for you?

In Topic: Command Line Section Failure

26 June 2010 - 07:37 PM

Probably not. I'm more confused over the (apparent) fact that there haven't been more reports based on this little stunt - Win7 isn't that new anymore, and I'm sure other BWP users must have it... Question is, now, if it's (legally, specifically) possible to include those files in the BWP installer distribution's utilities folder.

In Topic: Command Line Section Failure

26 June 2010 - 06:52 PM

@dabus:
I was more thinking of whether or not he could copy some misplaced command exes back into system32. And you're right about the "other things to script things" - I've been wondering if that Windows Power Shell did some funky things when it was installed, but I can't really imagine that.

In Topic: Command Line Section Failure

26 June 2010 - 06:25 PM

ComSpec=H:\Windows\system32\cmd.exe
Path=H:\Windows\system32;H:\Windows;H:\Windows\System32\Wbem;H:\Windows\System32\WindowsPowerShell\v1.0\;H:\Program Files\Common Files\DivX Shared\;H:\Program Files\QuickTime\QTSystem\
SystemDrive=H:
SystemRoot=H:\Windows
windir=H:\Windows

Hope this is what you need.


It is indeed, and it shows at least your environment is ok. Windows setup has always had a habit of making facepalm inducing decisions for drive letters when there were other drives present. Unfortunately, that doesn't explain why it chokes on a standard call to xcopy... :wall:

Can you please just do a search for xcopy.exe, findstr.exe (and what else, dabus?) and see if they exist anywhere on your system?

In Topic: Command Line Section Failure

26 June 2010 - 05:56 PM

Just to get some more info, could you please
- open a cmd window (hope that's the same on vista)
- type "set" (without quotes) and enter
- post the results, no matter if by screenshot or copypasted
? That should give a clue if your OS installation is actually being weird or not.