SomethingToChatWith

How about making it where the first 2 posts or so haft to be approved before they are even posted?

Can you still get into XP? Install EasyBCD there -> Manage bootloader -> Re-install Vista bootloader -> Write MBR. Still having trouble? Sometimes startup repair has to be used more than once to fix everything. You may also try the manual steps for rebuilding the bcd here.

Use startup repair from Windows 7 DVD. Get EasyBCD 2.0 beta build 63 or later from here and add entries for both Ubuntu/XP.

Simple, most places dont have dont display last username enabled, so a user account is already filled in for me. All I need to do is get in under a limitied user to use net user to get the information I need. Once i've discovered an account with admin access that isnt disabled, reboot real quick with kon-boot and get in.

Sounds like need to start charging lol Im just too nice to people I know.

Umm, can you say net user? You don't need admin access to get the usernames for the computer and I doubt you've enabled don't display last username so who cares if its not the welcome screen? Your username is already filled in by default. If you took the time to read through the thread you would have noticed patched XP machines and Vista safeguard against this escalation flaw in at by requring you to be admin to even use it.

edit: sorry, didnt see this post when I posted below. Delete if you want...

Anything I pirated I since went out and legally bought.

If you're goning to boot off something whats the point? I think kon-boot more than covers it.

Copy the files from existing XP installation media over to a fat32 formatted flash drive. Use bootsect to make it bootable.

Ok, tune in at 12:02. He used GCC to compile the code. There's an option you need to throw in (they show it briefly if you wanna pause it). Darren said there was a note somewhere about it but I didnt see it on the site.

Ok, the force option isnt needed to close your apps. In addition you may shutdown your computer without closing your apps, granted any hanging apps would stop it until you ended it. Like you I was commenting, so maybe if you tried it you would understand it.

Ovbiously Darren has for the episode. hak5Darren, how'd you go about it?

If frames are so looked down upon than whats the best replacement for them? They ovbiously have a purpose to some people.

How are you really shutting down your PC quicker anyhow? I notice you've got a 3 second delay in there for a silly message. You're best taking out the forcing everything to quit and limiting the time before it tries to shutdown to 0.

Yeah good luck. It would be nice if they put up a compiled version. They just assume all of us are hardcore coders.

Ok, it doesnt. Sometimes these type of files are executible. They've got a /docs dir that may come in handy. Bummer, I was going to try this out but like you I've got very limited experience compiling manually.

The download didn't come with a .bin file? Hmm... let me see if I can find it. As for compiling ovbiously you're missing something there or need to include a parameter with make.

If you're not modifying anything in the code use the pre-compiled bin and dd as shown on the episode to install it to a flash drive.

I don't get what it is about storing data on these laptops that are getting stolen. If the files stay on a NAS at the office than it wouldn't matter. People are asking for trouble.

Every 3 Tuesdays if its up to date :P

Ok, the at command can be used by a limited account even in XP SP2. Don't believe me? Type "at /?" at the command prompt. You should see the help output for at. Now while you cant actually "use" the at command beyond viewing the help this is an ovbious giveaway. The task scheduler service still runs under the SYSTEM account. With any luck what I'm thinking is MS only patched the at command itself. Even a limited user can create tasks using the GUI. So what does this mean? I'm wondering if you can take a pre-sp2 XP version of the at command and use it? If MS only patched the at command stored on the local system whos to say you couldn't use an older version of at from say a flash drive... And yes digip, you're right on there. The way anything involving proccesses in Windows works is that child proccesses always get the amount of system access the parent proccess (in this case at running as the system account) has.

You sure about that? I just got done trying it on my XP SP3 box without issue.

Wouldn't UAC protect against this? I'm amazed its that simple. And here people are thinking the screensaver login trick in 2000 was 1337.

In a batch, add this line before specifying the place to put files; it basically makes the root of the drive the working directory: cd\