H@L0_F00

No, because of the pound sign (#) in front, Grub4DOS doesn't "notice" it. It sounds like your menu.lst is actually menu.lst.txt. To view file extensions: - select Start > Control Panel > Folder Options - select the View tab - UNcheck "hide file extensions for known file types" - Click OK to finish If it is menu.lst.txt then you need to rename it to menu.lst

I doubt any school would care at all about a "disclaimer" and would without a doubt report you to the police as a hacker, especially if any real damage was done to the computer.

You can download different sizes of casper-rw files here: http://www.pendrivelinux.com/live-ubuntu-8...nstall-windows/ They're quite small zipped.

FreeDOS: remove "floppy" at the end of the initrd. Should be "initrd /freedos.img" SystemRescueCD: incorrect file name. "/rescuecd" should be "/rescuecd.img" Memtest86+: Where did you get that file? And why is it an .img? I've never seen an .img, only .bin. Also, have you tried mapping the ISOs? You can map ISOs without using memdisk like you have it with Kon-Boot.

Same here, only problem is it might (read would) come back to bite you in the ass when somebody is caught fucking with the computers at your school and they instantly give up your name :/

I think you guys might make quite a few bucks selling a premade USB Multipass with a Hak5 splash image, customization, etc. :)

Glad we could help

You can password protect your Multipass a couple different ways. You can also use both plain-text or a salted MD5 hash. To generate an MD5 hash of your preferred password 1. Boot up Grub4DOS 2. Press 'c' which brings you to the command line 3. Type in "md5crypt" and press Enter 4. It will ask you for a password, input your password. 5. The hash will be created, write it down EXACTLY HOW IT APPEARS. My USB-TestVM would work well with this so that you can type everything in on the host instead of having to write it all down which can be a pain when you have bad handwriting or can't always decipher your '5' from your 'S.' Now you've got a salted MD5 hash of your password, you can use this instead of plain-text for a little bit more security. (Although the password can EASILY be bypassed with a program as simple as notepad. More on that later.) Ok, now you must implement the password in your menu.lst (this can be used on any .lst file though). Let's say I use the password "multipass" and get the hash of "$1$vqP3$/KfP4fwz0nDBeFiEf0INP0" To password protect editing of the boot options at the Grub4DOS boot (where it shows your menu.lst) default 0 splashimage /multiboot/splashimages/tux.xpm.gz password --md5 $1$vqP3$/KfP4fwz0nDBeFiEf0INP0 This requires the user to "gain privileged control" before editing any of the listed boot options or using the command line. To gain privileged control press 'p', type in your password, and press Enter. Now you can edit the boot options and have access to the command line. You can make it so the user must gain privileged control before executing any of the boot options by using the "lock" command in your boot sequence like this: (Note-you must have a password set at the beginning of the config file (posted above) to use this) title Something lock kernel /multiboot/something/vmlinuz initrd /multiboot/something/initrd.gz Now, if you try to boot "Something" you are denied "Error 32: Must be authenticated" which you solve by authenticating (pressing 'p' and typing in your password). You can add the "lock" command to any boot sequence, just remember that it stops executing when it reaches the "lock" command, so if you put it at the end, it's still bootable without authentication. To request a password when the boot option is selected title Something password --md5 $1$vqP3$/KfP4fwz0nDBeFiEf0INP0 kernel /multiboot/something/vmlinuz initrd /multiboot/something/initrd.gz This will ask for a password when booting "Something" resulting in Error 32 if the password is incorrect. If I wanted, I could replace anywhere where it says "password --md5 $1$vqP3$/KfP4fwz0nDBeFiEf0INP0" with "password multipass" and it will do the exact same thing, except your password is then in plain-text in your menu.lst file. I don't know why you'd want to do this, but you can, so I put it out there. Although this does offer some type of "protection" from unwanted use of your multipass, to bypass it somebody could easily remove the "password" line and they're in. This does not encrypt, hide, or in any other way protect your data, everything is still on you flash drive and the password can be removed by an idiot.

Thanks, glad you all find it useful. :) Have you tried reinstalling Grub4DOS?

You make the floppy image yourself using the dban-1.0.7_i386.exe file found here. My image file is here, if you'd rather use that. Images can be compressed using the gzip method and loaded directly from the *.gz file. This works great because most floppy image files aren't 1.44 MB, such as Kon-Boot which I compressed to like 10 Kb I think. 7-Zip works great for this in Windows. And I'm still not sure what you mean about where exactly the errors are shown. Now that you removed the '=' your USB boots to your menu.lst? Or does nothing happen, you can't see your menu at all and you just get the error?

Bowser cookies?

The files would have to be converted. Not sure about windows, but if you can run a linux distro you can use the "file" command and point it towards your ISO/img file and it should be able to tell you what it is. Changing a file extension doesn't change the format. It sounds like your problem is with the booting of Grub4DOS though. What is it exactly that happens when you boot it? Do you ever even see your menu?

I've rezipped and reuploaded the USB-TestVM due to a couple people having problems with it. I've also add the BIOS file because I accidentally left it out last time and discovered that if you installed an OS it would try to boot the HDD first. The link is to the new VM, the old ones have been deleted. The Virustotal scan is also for the new VM. What it contains: USB-TestVM (dir) --plpbt.iso--PLoP Bootmanager which allows you to boot a flash drive from a VM --USB-TestVM.vmx--VM configuration file --USB-TestVM.vmxf--VM team member file --USB-TestVM.vmdk--VM disk file (8GB) --USB-TestVM.nvram--VM BIOS file There is NO operating system on the VM disk file. Created using VMware Workstation 6.5. It runs without a hitch in VMware Player, so you don't have to buy/pirate anything, just download Player and load the .vmx file. The VM is set to autoconnect all mass storage USB drives, and the BIOS are set to boot from the PLoP ISO. Instructions: Extract the zip file Power-on the VM using the .vmx file You'll be greeted by the PLoP Bootmanager Wait until you see that your USB drive is connected (bottom right, suitcase-looking thing should be solid, not transparent) Go down to the "USB" option and press "Enter" There you go, test your flash drive You can still install an OS, such as Windows XP to test Kon-Boot or Ophcrack, but including that would be illegal warez so do it yourself, k? k. USB-TestVM -> http://www.mediafire.com/?oydn0xngdlz VMware Player -> http://www.vmware.com/products/player/ VMware Player (DDL) -> http://download3.vmware.com/software/vmpla....5.3-185404.exe PLoP Bootmanager -> http://www.plop.at/en/bootmanager.html And for everybody who cares, Virustotal -> http://www.virustotal.com/analisis/294dcd3...4fdf-1251343898 If the file is removed due to not enough constant downloads, PM me and I'll get it back up. I'd appreciate feedback if you could, thanks. EDIT: 8/29 - Added VMware 2.5 Player direct download link, thanks to nicatronTg.

Ahh, well I like viewing my "Protected" OS files lol But yes, because Mac OS is based on UNIX files starting with a '.' are hidden, the only problem with that is that some folders/files can't be moved or renamed (as of now) such as "casper." The "invisible bit" the mention in the link you posted are HFS+ proprietary, which means they can't be used on a FAT32 drive. What I did was use a program called "setfile" on an OS X system which makes a file that holds all HFS+ metadata for the specified file on a non-HFS+ filesystem. Essentially this adds more files, which are hidden by default in windows, but I'd rather have spotless looking drive when my teachers/fellow students see it.

All files/folders on the root of mine are hidden as well, it doesn't reduce clutter on my personal computer because I like knowing what's on my computer so "View hidden files/folders" is enabled :P I mainly hid them so they won't show up when using my flash drive at school. I just feel more comfortable having other students and teachers not thinking "what the hell is "multiboot? or casper?" " especially if I were to plug it into a teachers computer for a presentation or something while the projector is on. :o We actually have more Macs at school than PCs in use so I had to figure out how I could hide the files on a Mac as well, which I did. :) If anybody would like to know how, PM me.

To enter the Grub4DOS command line you can simple press 'c' at anytime, you do not need to use "commandline." Also, if you'd like to view a file with say, Windows keys or something instead of writing them all down you can use this: title Windows Keys cat /Windows-installs/keys.txt pause configfile /menu.lst "/Windows-installs/keys.txt" can be changed to any file you'd like, "pause" temporarily stops the script from executing until you press a key so that you can actually read the text displayed (and write anything down if you'd like), and "configfile /menu.lst" just brings you back to the first boot menu. I'm working on editing the init scripts in both Ophcrack and Back|Track 4. When I get all the kinks worked out you should be able to place the Ophcrack tables in any directory you'd like and have Ophcrack still start up automatically and you should be able to move the "casper" directory off the root of the flash drive and put those wherever you'd like and still be able to boot BT4. This will decrease clutter on the root of the drive as well as make it possible to boot multiple distros that implement the casper temporary file system.

Ahh I see, glad it works. Thanks for the feedback.

So nothing boots except Kon-Boot in the VM, but everything else boots fine on your real hardware? Can you post the line at which the boot sequence fails? It appears above the error line. Also, what does it say after "Error 5:"? because there's almost always some sort of description of why it failed.

Correct grammar, punctuation, and word selection, please? I don't understand this at all.

Same here but if it works, it works, right? haha I'll give it a try and post what happens.

I haven't gotten around to testing it, I don't really need TRK, but I'll test it sometime in the near future, probably within a week. Have you tried the multi-partition method? I don't see how that could fail at all as long as it was done correctly and the machine can actually boot from USB.

Thread Pick one:

Yeah, no. I'm not elitist. I help were I can if I see that there was an effort made by the person asking. You don't learn by the answers being given to you, you learn by discovering the answers yourself. There's no point in more posts when everything has already been answered. I tried to help you, you just took it too personal I guess. If you feel I'm being elitist and plan on continuing this pointless argument than I'll gladly step back and we can wait for somebody else to help you. Insulting people who are trying to help and know a bit about what they're doing is not the way to make progress.

Here's what I know: Basic: to get the job done quick and easy. Not a lot to learn. Java: Meant to be cross-platform (although I hear everybody says there's always problems with it's portability). C++: Cross-platform. No need for memory management as in C which usually means less work and less exploits. Python: Cross-platform, quick scripting language. Essentially they were all created with a couple things in mind: Ease of use, faster development, portability, and improvements upon it's predecessors.

I had to say it, there's been too many people not even reading this post and asking to be spoon-fed the answers which have already been covered in this topic. What led me to believe that you didn't try them all is that you didn't mention anything about multipartitioning your flash drive which was mentioned here already, and you also didn't have the "vollabel=" parameter appended to your kernel option which was also posted here already: Have the other things I recommended worked out your problems? If not, post the post the "fail line" which I talked about in my previous post. EDIT: Elitist? Far from it. Tired of people not trying to figure out their own problems? Yes.