View Single Post
  #1773 (permalink)  
Old 03-26-2009, 05:58 PM
rainabba's Avatar
rainabba
PPCGeeks Regular
Offline
Location: Phoenix
 
Join Date: Apr 2008
Posts: 172
Reputation: 270
rainabba is becoming a PPCGeeks regularrainabba is becoming a PPCGeeks regularrainabba is becoming a PPCGeeks regular
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: WM 6.5 Kitchen QVGA and VGA Developer Edition

Quote:
Originally Posted by Tplane37 View Post
Dan:

Did you get the "Acces to *.dsm denied" error in PPCK? I just DLed ur files and have not tested them. But that is where I got hung up on 21195 and 21198. If so, how did you get around it/fix it? It looks to be in <SYS_21198_Common> but I am not sure. I have verified that there is no request for the file in my <option.xml>. Basically, I am lost and have been looking around for a way to correct the issue, with no luck obviously.

Had the same error for 21193, but all I had to do was copy the *.dsm file manually from <orig_*> to <*temp> in my Aplications Data folder. But in 21195 and 21198, the requested *.dsm is not on my PC anywhere (And do you know how long it takes to use the "Search" function on 6 TB???? A LONG time!)
I dealt with that quite a bit the other day and it was one of two things. Either a module had both a file and folder of the same name when it should only have the folder. For example, mscoree.dll which is part of .Net was one that gave me trouble.

The 2nd cause is actually directly related to the first I think. If your SYS contains a module in folder form, but another kitchen has it in file form, you see this.

Ultimately I think it's because Vista freaks out when you ask it to overwrite a file with a folder of the same name. File -> File or Folder -> Folder is fine, but not one to the other.

My solution was to clean out file instances or entire modules from SYS when they existed somewhere else.

EDIT: After reading Drellisdee's response, I'm remembering another issue I had and perhaps this was what I experienced. Following are other steps I took that ultimately did the trick, though I'm not positive which did it.
  • "Take Ownership" of your temp folder. Though this should already be done, in my case it wasn't and I have no explanation (and I'm the domain admin)
  • Drop to a cmd window. CD to the \Kitchens folder, and run "attrib -H -S -R *.* /S /D" to ensure all files are visible, and writable.
  • Consider leaving the 2119x SYS folders expanded instead of archived. (Thanks to dan-htc for that tip). Things run quicker and it saves you time setting things up.

Last edited by rainabba; 03-26-2009 at 06:04 PM.
Reply With Quote
This post has been thanked 1 times.