"MSVCP100.dll file" not found on Windows XP Pro

[John Gray]

Trying ShadowSpawn on Windows XP Pro give me that error message.

I used the files from ShadowSpawn-0.1.0-x86-XP.zip
and ran vcredist_x86.exe.

Thanks!

[Craig Andera]

> Trying ShadowSpawn on Windows XP Pro give me that error message.
>
> I used the files from ShadowSpawn-0.1.0-x86-XP.zip
> and ran vcredist_x86.exe.

It appears as though we may have uploaded the wrong version of the VC
redist. Sorry about that! I've uploaded the correct version to
https://github.com/candera/shadowspawn/downloads. Can you give it a
try and let us know if it works.

Thanks!

[John Gray]

On Jul 27, 11:33 am, Craig Andera <cand...@wangdera.com> wrote:
> > Trying ShadowSpawn on Windows XP Pro give me that error message.
>
> > I used the files from ShadowSpawn-0.1.0-x86-XP.zip
> > and ran vcredist_x86.exe.
>
> It appears as though we may have uploaded the wrong version of the VC

> redist. Sorry about that! I've uploaded the correct version tohttps://github.com/candera/shadowspawn/downloads. Can you give it a

> try and let us know if it works.
>
> Thanks!

On Jul 27, 11:33 am, Craig Andera <cand...@wangdera.com> wrote:
> > Trying ShadowSpawn on Windows XP Pro give me that error message.
>
> > I used the files from ShadowSpawn-0.1.0-x86-XP.zip
> > and ran vcredist_x86.exe.
>
> It appears as though we may have uploaded the wrong version of the VC

> redist. Sorry about that! I've uploaded the correct version tohttps://github.com/candera/shadowspawn/downloads. Can you give it a

> try and let us know if it works.
>
> Thanks!

Yes, using the 2010 version rather than the 2005 version works fine,
thanks!

I have found another snaglet. I made an error in the command line,
and ShadowSpawn 'hung', and I had to Ctrl+Break out of it. This
leaves the drive letter showing in Windows Explorer as Local Disk
(Q:), and a re-execution fails with
Error: Device already exists. Device = Q:

net use q: /d
gives "The network connection cannot be found", and Windows Explorer
gives no way (that I know of!) to delete the Local Disk.

So two questions:
a) how can I retrieve my drive letter q: for use?
b) could ShadowSpawn on starting neatly handle the problem where the
supplied drive letter is in error? (And obviously not disconnect a
'real' disk...!)

Thanks

[Craig Andera]

> I have found another snaglet.  I made an error in the command line,
> and ShadowSpawn 'hung', and I had to Ctrl+Break out of it.  This
> leaves the drive letter showing in Windows Explorer as Local Disk
> (Q:), and a re-execution fails with
> Error: Device already exists.  Device = Q:
>
> net use q: /d
> gives "The network connection cannot be found", and Windows Explorer
> gives no way (that I know of!) to delete the Local Disk.
>
> So two questions:
> a) how can I retrieve my drive letter q: for use?
> b) could ShadowSpawn on starting neatly handle the problem where the
> supplied drive letter is in error?  (And obviously not disconnect a
> 'real' disk...!)

I don't know whether we can handle ctrl-break. We try to handle ctrl-c
gracefully, but I'm not entirely sure it's working correctly.

To recover your drive letter, a reboot will definitely handle it. You
*might* be able to just log out and log in again - I'm not sure on
that one. I realize rebooting is a lame workaround - I've added issues
#5 and #6 to address these problems.

https://github.com/candera/shadowspawn/issues/5
https://github.com/candera/shadowspawn/issues/6