Right,
Well the iso was created alright and the cd started working but only to get to the point where I get a message that network support has not started yet, do u want to start now? If I say no, then it just stays idle and if I say yes it comes up with a PE Network Configurator-Network Profiles screen. Here I 'm asked to select a network profile to use in automating network settings and it ends up unable to install network adapters. Any hints about this one?

The newest release of BartPE is different than the previous versions in how it handles drivers. In our previous releases of the CD, all of the drivers that we have accumulated were included. But now BartPE parses the drivers differently and thus we will shortly be releasing a "driver add-on" download which will purely be drivers. Thus, meaning that the current release of our CD (2.4) doesn't have any of the drivers from the previous releases included. We are sorry for the inconvenience but due to the new format of BartPE, it's taking time to get the drivers ready. We'll have the driver download available soon of which you'll then add to the build before making the ISO/CD. Then, most, if not all, network cards, among other things, should work fine. Thanks.

You still can do anything else though with the programs, you just can't get connected to the internet.

You post another issue now. Did our help with your first issue fix it?? I would appreciate a response in your first post! This type of behavior does not help the project and I would appreciate a response in your first post. As for your NIC issue, I will be glad to build you a driver plugin if you provide specs on your NIC. Such as Manufacturer and model number. That is how the drivers issue is being handled, it's been posted in the forum several times and in the "news" on the site? Doesn't anyone read what I write??

Hi,
I'm sorry for storming in this forum with all these questions out of nowhere and for being lame with this whole thing.
I started building the ubcd and took me a couple of days cause I have no idea what I am doing. I've managed to run it but I'm still comfused. What I am trying to do is bypass the adminstator password. Do I even need the nic drivers? Or should the cd cover what I want to do anyway? I've tried running the password renew from the recovery tools but didn't get anywhere with that.

Yes, you don't need the NIC drivers if all you're doing is trying to change the admin password. I've just tried to use password renew myself on an installation of XP and found that it didn't actually change the passwords as it said it did. I don't know why that happened, but when I ram SAMInside to crack the admin passwords (as the new ones weren't working), after running for about 15 minutes checking like 5 x 10 million passwords a second, it cracked the password and it was still set to my old password. Anyway, when you're in the CD, there aren't really any restrictions, you are the admin of everything there. So I hope that helps.

Don't worry about it. We just appreciate replies back letting us know if we actually helped you or if you need more help. I do have to say I admire the fact that you did not become discouraged when it took you a few days to figure out how to build the project. Some people just give up after having one or two little issues.

I have received many positive emails from people who had success with Password Renew, so I don't quite understand why it isn't working for you two. Although LittlBUGer does offer another good way to get your password.

Finally, please let me know what NIC you have in your system. I would be glad to create a driver for it so I can include it in the "driver" download that should be released soon!

Where I 'm trying to be an admistrator in is my own initial windows environment from where I was kicked out originally. The restriction in the case is that I can't access all my data. I'm running the ubcd as a boot cd.

I was barred from logging on to windows xp after trying to delete some virus files.

In order to regain access to my windows without formatting, as far as my understanding goes, I needed to run the recovery mode from the windows xp cd. I couldn't do that though because of this administrator password request.

I'm trying to use the ubcd to find a way around this password request I'm asked for in recovery mode from windows xp. I have run Password Renew a couple of times now. When I go back to the recovery from the windows xp cd, the new pass still doesn't work.


I have no idea how you ram SAMInside in order to crack the admin pass? Sorry mate but this one just goes beyond my reach.

Here's the quick way to run SAMInside:

Once booted into the CD, go to Programs -> System Tools -> InsidePro Tools -> SAMInside. Once it's loaded, go to File -> Import SAM-file... Then you can either browse to your HD and go to C:\Windows\system32\config and click and open the SAM file or just type it in and click open, such as (if C: was your main HD)

NOTE: You may need to change Windows to WINNT, depending on your installation.

Then it might say the SAM file is additionally encrypted with the SYSKEY algorithm. So now you need to open the SYSTEM file located in the same place.

Once you do that, it should now show all of the user (or maybe just Admins) on that computer with checkboxes next to each. You can uncheck the Guest, SUPPORT, and HelpAssistant ones as those aren't needed. The main one you want is the Administrator one if you want to access the Recovery Console but you can also do other ones as well.

Now comes the fun part. There are three different ways of "cracking" the password---either by brute force, masking, or by dictionary. If you absolutely know part of the password already, then type it into the little password text box at the bottom of the window and go to Search -> Mask attack -> Start on LM Hashes... Then just give it lots of time to try and find the password. If you don't know it at all, you can either try the dictionary approach or the brute-force. Dictionary may not take as long as brute-force, but you're not likely to get the password. I would suggest doing them on the LM Hashes first and if it finds nothing after a long time, then try the NT Hashes (though usually they are in the LM Hashes.

Depending on your system, it could take a long time to find/crack the password. I know that on my Athlon FX-53 system, it said it was going at 3 x 10,000,000 p/s (passwords per second and 5 being the number of users I was trying to crack), but every system will differ. It will take lots of time, so just sit back and do something else while it goes. The stronger the password, the longer it takes. The passwords will probably start showing themselves in bits and pieces until it finds the whole thing.

Anyway, I hope that helps. It's a great program, even though it's time consuming. I'm disappointed that the Password Renew didn't work at all. Oh well...

when trying to open C:\Windows\system32\config\SAM a SAMInside window stops me saying 'A sharing violation occured while accessing C:\Windows\system32\config\SAM' and the file doesn't open.

You receive this message when you try that option when booted with the CD?

If you booted from the CD, you shouldn't have any problems. Only in Windows will you have a problem like that, as Windows wont let you access it while running...

Yes I have booted from the ubcd, run SAMInside and this is the message I get. It must be my golden luck these days I suppose.

I'm gonna try bypassing the password by booting from a windows 2000 cd. Apparently there's no password request when running recovery from this cd and it should just let me in windows xp. Here is a link reffering how this should work http://pubs.logicalexpressions.com/Pub0009...icle.asp?ID=173.
I'll post any progress.

Cheers,
Vas.