Jump to content


Photo

CMD Crash


  • Please log in to reply
2 replies to this topic

#1 Lord_Jeremy

Lord_Jeremy
  • Member
  • 22 posts

Posted 30 March 2011 - 08:25 PM

My first attempt to use the BWP Setup/Install suite was in a wine system, but that ultimately failed. I've since been running the setup on my Windows 7 x64 machine. I disabled UAC and installed BG/II in a directory outside program files, etc. The installation was progressing fine, but during the BAT script process, the system started making a rapid beeping sound. The CMD title said "ToA\mp3\ZNOMOR59.mp3 - mpg123/w32 0.59s-mh2 (Not Responding)". The CMD window was filled with gibberish text. The debug log, however, was still being updated with progress from the WeiDU mods. The CMD window is frozen but as long as I don't have to do any more interaction, I think the install will complete fine. I guess CMD somehow crashed. Unfortunately, before I thought to check the debug log I did open Resource Monitor and killed one of the child processes (setup-kivan.exe) that was spawned by CMD. I don't know what that process was in the middle of, or whether or not it was done by the time the system killed it. Would it be possible for me to uninstall or reinstall just that WeiDU mod? I'm guessing I shouldn't just remove that mod through normal WeiDU use because I remember reading that the BWP system doesn't jive with the regular WeiDU backup and install order control. I suppose if it came down to it I could manually remove any scripts or creature files related to the Kivan mod, as to prevent encountering him and possibly running into a bug. Any suggestions?

#2 Karmapowered

Karmapowered
  • Member
  • 42 posts

Posted 30 March 2011 - 09:09 PM

Please check out this thread, as your issue seem very much related to me.

I hope this helps.

#3 Lord_Jeremy

Lord_Jeremy
  • Member
  • 22 posts

Posted 31 March 2011 - 06:30 AM

Ah, thank you very much! I had done a couple google searches and I figured that would encompass the forum, and it was a weird enough issue it was possibly just me. Anyway, I just replaced the oggdec.exe and I'm running the install again.