Guest Twayne Posted August 20, 2008 Posted August 20, 2008 X'd to .general & .security_admin Hi, ntbackup, defrag and even Ghost are having trouble locking up at System Volume Information on an XP Home computer, and probably other things are too. Before I do a backup restore that might have the same issue, thought I'd ask: XP Home: Programs halt on c:\system volume information\mountpointmanagerremotedatabase. This problem is all over the 'net in thousands of places and the "usual" fix it to delete the errant file and let it be recreated. I can easily see how I'd do that in XP Pro by exposing System Volume Information and adding myself for access to it. But, XP Home seems to have no such way to "take ownership" or whatever you want to call it. There is no way I can find to be able to see or work with System Volume Information contents. I was hoping someone here could assist me with accessing Home's System Volume Information? Sure appreciate it. On my XP Pro machine I can see what's in it fine; besides itself, a log file and a CID of some kind. On the XP Home machine, using ntbackup, I can get a look at the contents of it (every other method results in a denial of access) and there is no log, but a long list of RPxx files. So, it looks like deleting it would let me start over again. They live in a folder called _restore(F5.....). I assume, since that doesn't exist on the Pro machine, that the prevailing advice in the forums et al to delete everything and let it be recreated might be the proper answer. But only SYSTEM has access to it; I can find no way to add myself to the access abilities as I can in Pro. Any help? TIA for any advice/assistance. FYI, ntbackup is handy to let you get a look at what's in lots of denied system areas in XP Home Twayne
Guest Nepatsfan Posted August 20, 2008 Posted August 20, 2008 Re: XP Home backup problem "Twayne" <nobody@devnull.spamcop.net> wrote in message news:eTppN1uAJHA.3756@TK2MSFTNGP03.phx.gbl... > X'd to .general & .security_admin > > Hi, > ntbackup, defrag and even Ghost are having trouble locking up at System Volume > Information on an XP Home computer, and probably other things are too. Before > I do a backup restore that might have the same issue, thought I'd ask: > > XP Home: Programs halt on c:\system volume > information\mountpointmanagerremotedatabase. > This problem is all over the 'net in thousands of places and the "usual" fix > it to delete the errant file and let it be recreated. I can easily see how > I'd do that in XP Pro by exposing System Volume Information and adding myself > for access to it. > > But, XP Home seems to have no such way to "take ownership" or whatever you > want to call it. There is no way I can find to be able to see or work with > System Volume Information contents. > > I was hoping someone here could assist me with accessing Home's System Volume > Information? > Sure appreciate it. > > On my XP Pro machine I can see what's in it fine; besides itself, a log file > and a CID of some kind. > On the XP Home machine, using ntbackup, I can get a look at the contents of > it (every other method results in a denial of access) and there is no log, but > a long list of RPxx files. So, it looks like deleting it would let me start > over again. They live in a folder called _restore(F5.....). I assume, since > that doesn't exist on the Pro machine, that the prevailing advice in the > forums et al to delete everything and let it be recreated might be the proper > answer. But only SYSTEM has access to it; I can find no way to add myself to > the access abilities as I can in Pro. Any help? > > TIA for any advice/assistance. > FYI, ntbackup is handy to let you get a look at what's in lots of denied > system areas in XP Home > > Twayne > > > Boot the XP Home Edition computer into Safe Mode and log on with an account that is a member of the Administrators group. You should now have access to the Security tab on the System Volume Information folder. You can take ownership and give the Administrators group Full Control permissions to the folder and its contents. Good luck Nepatsfan
Guest Twayne Posted August 20, 2008 Posted August 20, 2008 Re: XP Home backup problem > "Twayne" <nobody@devnull.spamcop.net> wrote in message > news:eTppN1uAJHA.3756@TK2MSFTNGP03.phx.gbl... >> X'd to .general & .security_admin >> >> Hi, >> ntbackup, defrag and even Ghost are having trouble locking up at >> System Volume Information on an XP Home computer, and probably other >> things are too. Before I do a backup restore that might have the >> same issue, thought I'd ask: XP Home: Programs halt on c:\system >> volume >> information\mountpointmanagerremotedatabase. >> This problem is all over the 'net in thousands of places and the >> "usual" fix it to delete the errant file and let it be recreated. I >> can easily see how I'd do that in XP Pro by exposing System Volume >> Information and adding myself for access to it. >> >> But, XP Home seems to have no such way to "take ownership" or >> whatever you want to call it. There is no way I can find to be able >> to see or work with System Volume Information contents. >> >> I was hoping someone here could assist me with accessing Home's >> System Volume Information? >> Sure appreciate it. >> >> On my XP Pro machine I can see what's in it fine; besides itself, a >> log file and a CID of some kind. >> On the XP Home machine, using ntbackup, I can get a look at the >> contents of it (every other method results in a denial of access) >> and there is no log, but a long list of RPxx files. So, it looks >> like deleting it would let me start over again. They live in a >> folder called _restore(F5.....). I assume, since that doesn't exist >> on the Pro machine, that the prevailing advice in the forums et al >> to delete everything and let it be recreated might be the proper >> answer. But only SYSTEM has access to it; I can find no way to add >> myself to the access abilities as I can in Pro. Any help? TIA for >> any advice/assistance. >> FYI, ntbackup is handy to let you get a look at what's in lots of >> denied system areas in XP Home >> >> Twayne >> >> >> > > > Boot the XP Home Edition computer into Safe Mode and log on with an > account that is a member of the Administrators group. > You should now have access to the Security tab on the System Volume > Information folder. You can take ownership and give the > Administrators group Full Control permissions to the folder and its > contents. > Good luck > > Nepatsfan Nepatsfan, you have once again come to the aid of the needy! THANKS MUCH! I knew there was a way, but ... It didn't work at first but not because of forgetting to turn on seeing system files or anything like that. I *think* it's because the computer I'm working on is a Walmart "Special"; a Balance Technologies computer so poorly put together I could write a book on it if I weren't careful. First I went to Safe Mode find, saw all the files I expected, etc., EXCEPT System Volume Information! Checking another folder though, I did see that Simple File Sharing was indeed shut off now, and I DID have the Security tab I needed. But the folder was nowhere to be seen! Long story short, I went to my XP Home laptop and checked it; all was as expected, including the VIF being visible. So, back to the Walmart special. One of the things I discovered in my travels of trying to figure out why hyper-threading wasn't working was that it's "uniprocessor" Intel Celeron, not ACPL or whatever the right phrase is. OK, so what could that mean? On a hunch, I did a Search for System Volume Information and there it was! So I was in! As long as you KNOW what it is you want to see, you can manage to "see" it by searching for it with Explorer. But it will NOT be listed in the folders views, no matter what. And yes, I triple checked all the View settings in Tools was set to see system files. So, apparently with the uniprocessor, you don't get to see ALL the files, no matter what you do. That was all news to me! Not that it's the only rude surprise that processor gave me! At any rate, it's fixed and everything works again. All I did was turn off Restore and delete the MountPointManagerRemoteDatabase file. I still have NO Idea why it did what it did to me, how it got set that way, or why deleting fixes it (it's a 0 length file), but it's up and running perfectly again. Searching MS was no help, either. Dunno if any of that info is useful to you or anyone reading or not but thought I'd mention it. Oh, and BTW, XP's System Information will not show you that it is a uniprocessor that I can see. You have to use a program like SIW or one of the more inclusive sys info apps to see that. I specifically used siw.exe; excellent app. Regards, & thanks again, Twayne
Guest Nepatsfan Posted August 20, 2008 Posted August 20, 2008 Re: XP Home backup problem "Twayne" <nobody@devnull.spamcop.net> wrote in message news:%23d3mW1wAJHA.1396@TK2MSFTNGP05.phx.gbl... >> "Twayne" <nobody@devnull.spamcop.net> wrote in message >> news:eTppN1uAJHA.3756@TK2MSFTNGP03.phx.gbl... >>> X'd to .general & .security_admin >>> >>> Hi, >>> ntbackup, defrag and even Ghost are having trouble locking up at >>> System Volume Information on an XP Home computer, and probably other >>> things are too. Before I do a backup restore that might have the >>> same issue, thought I'd ask: XP Home: Programs halt on c:\system volume >>> information\mountpointmanagerremotedatabase. >>> This problem is all over the 'net in thousands of places and the >>> "usual" fix it to delete the errant file and let it be recreated. I >>> can easily see how I'd do that in XP Pro by exposing System Volume >>> Information and adding myself for access to it. >>> >>> But, XP Home seems to have no such way to "take ownership" or >>> whatever you want to call it. There is no way I can find to be able >>> to see or work with System Volume Information contents. >>> >>> I was hoping someone here could assist me with accessing Home's >>> System Volume Information? >>> Sure appreciate it. >>> >>> On my XP Pro machine I can see what's in it fine; besides itself, a >>> log file and a CID of some kind. >>> On the XP Home machine, using ntbackup, I can get a look at the >>> contents of it (every other method results in a denial of access) >>> and there is no log, but a long list of RPxx files. So, it looks >>> like deleting it would let me start over again. They live in a >>> folder called _restore(F5.....). I assume, since that doesn't exist >>> on the Pro machine, that the prevailing advice in the forums et al >>> to delete everything and let it be recreated might be the proper >>> answer. But only SYSTEM has access to it; I can find no way to add >>> myself to the access abilities as I can in Pro. Any help? TIA for any >>> advice/assistance. >>> FYI, ntbackup is handy to let you get a look at what's in lots of >>> denied system areas in XP Home >>> >>> Twayne >>> >>> >>> >> >> >> Boot the XP Home Edition computer into Safe Mode and log on with an >> account that is a member of the Administrators group. >> You should now have access to the Security tab on the System Volume >> Information folder. You can take ownership and give the >> Administrators group Full Control permissions to the folder and its >> contents. >> Good luck >> >> Nepatsfan > > Nepatsfan, you have once again come to the aid of the needy! THANKS MUCH! > I knew there was a way, but ... > > It didn't work at first but not because of forgetting to turn on seeing system > files or anything like that. I *think* it's because the computer I'm working > on is a Walmart "Special"; a Balance Technologies computer so poorly put > together I could write a book on it if I weren't careful. > First I went to Safe Mode find, saw all the files I expected, etc., EXCEPT > System Volume Information! Checking another folder though, I did see that > Simple File Sharing was indeed shut off now, and I DID have the Security tab I > needed. But the folder was nowhere to be seen! > Long story short, I went to my XP Home laptop and checked it; all was as > expected, including the VIF being visible. So, back to the Walmart special. > One of the things I discovered in my travels of trying to figure out why > hyper-threading wasn't working was that it's "uniprocessor" Intel Celeron, not > ACPL or whatever the right phrase is. OK, so what could that mean? > On a hunch, I did a Search for System Volume Information and there it was! > So I was in! As long as you KNOW what it is you want to see, you can manage > to "see" it by searching for it with Explorer. But it will NOT be listed in > the folders views, no matter what. And yes, I triple checked all the View > settings in Tools was set to see system files. So, apparently with the > uniprocessor, you don't get to see ALL the files, no matter what you do. That > was all news to me! Not that it's the only rude surprise that processor gave > me! > At any rate, it's fixed and everything works again. All I did was turn off > Restore and delete the MountPointManagerRemoteDatabase file. > I still have NO Idea why it did what it did to me, how it got set that way, > or why deleting fixes it (it's a 0 length file), but it's up and running > perfectly again. Searching MS was no help, either. > > Dunno if any of that info is useful to you or anyone reading or not but > thought I'd mention it. > Oh, and BTW, XP's System Information will not show you that it is a > uniprocessor that I can see. You have to use a program like SIW or one of the > more inclusive sys info apps to see that. I specifically used siw.exe; > excellent app. > > Regards, & thanks again, > > Twayne > > > You're welcome. Nepatsfan
Recommended Posts