• iH8U
  • DriverPacks newbie
  • Offline
  • Registered: 2006-07-19
  • Posts: 2

Topic: SOLVED: bin\cmdow.exe could not be copied

hi to all, it's my first time here (my first post also). I'm always receiving this error when i try to slipstream the driverpacks:

Critical error! could not copy bin\cmdow.exe to \$OEM$\$1

I'm trying to integrate the DPacks to an NLite'd XP SP2 installation. What will I do?
Thanks.

Last edited by Bâshrat the Sneaky (2006-07-26 02:45:10)

  • Helmi
  • Moderator & Translator (German)
  • Offline
  • From: Germany
  • Registered: 2006-05-27
  • Posts: 1,799

Re: SOLVED: bin\cmdow.exe could not be copied

Running any virus scanner with auto-scan in the background?

http://d1syubgj0w3cyv.cloudfront.net/cdn/farfuture/AeXmpESLemRyQ4RE-dgdjRhN_hKaXMe7woWjOK2wsnk/perpetual:forever/userbar/moderator-3.png

Coming up next - useful links:
• If you like this project, please support it with your donation!      • Grab your HW info (HWIDs) here!     
• If you are a newbie, be sure to check out the DriverPacks tutorial!     • Here's how to create your own DP!
  • iH8U
  • DriverPacks newbie
  • Offline
  • Registered: 2006-07-19
  • Posts: 2

Re: SOLVED: bin\cmdow.exe could not be copied

Yeah, on my first NLite try, Symantec blocked it and reported that it is a hack tool. Deleted all and started my slipstream again (all updates, hotfix, and some tweaks) with the autoprotect of Symantec disabled. Everything went fine.

Now, when I tried to integrate the DPacks, that's the error I get. Am wondering what's wrong.

  • From: Hasselt, Belgium
  • Registered: 2006-05-26
  • Posts: 2,609

Re: SOLVED: bin\cmdow.exe could not be copied

Whatever the exact issue was (probably it was your AV which had quarantined the file and therefore it would no longer be available), it will be solved in the next version (6.07), since cmdow.exe won't be used anymore thanks to the new DriverPacks Finisher. Bye bye batch files. smile

Founder of DriverPacks.net — wimleers.com

Wim Leers's Website