First and foremost you need to decide what you want to replace your U3 software with. there are several programs that can run a file on a different drive, but the one i find is MOST user friendly is an Open Source Program Called u3-Autorun not only is it lightweight it will also let you run ANY program that you want by simply changing the proper line in the u3-autorun.ini that you place on the root of your drive.
now if you choose to use the u3autorun program then you can also change the icon of the "CD-ROM" part of your device by changing the autorun.inf and adding the appropriate icon to the cruzer-autorun.iso
After you choose what you wish to replace your U3 software with you *MUST* backup your U3 enabled device, because when you change the "CD-ROM" part of your device you will be repartitioning it to fit your replacement programs
the tool used to repartition/reload your u3 enabled device is called u3-tool
first figure out which drive letter your U3 CD-ROM is on(i will use J: in my example)
second open a properties window on the iso for which you using to replace the u3 software and write down the Size of the file...in the case of the cruzer-autorun.iso(version 0.9.2) the size is 124,928
next make sure u3-tool and your .iso file are in the same folder(this just makes things simple...and yes the desktop or the root of any drive works just fine
Now you must run cmd(start->run->type "cmd" without the quotes in the box and then click ok) and navagate to the location you put u3-tool and your .iso
after navagating to the directory you have the files in your first command will be(no commas or colons)
- u3-tool -p {size of .iso} {drive letter of your U3CDROM}
- Example "u3-tool -p 124928 j"
this tells u3-tool to repartition the u3cdrom to 124,928 bytes.
the next command will be(again no commas or colons)
- u3-tool -l {name of cdimage/.iso} {Drive Letter of U3CDROM}
- Example "u3-tool -l cruzer-autorun.iso j"
This tells u3-tool to load cruzer-autorun.iso onto the U3CDROM
now remove and reinsert your U3 Device.
now copy the u3-autorun.ini.samp to the root of the removable device and rename it u3-autorun.ini.
edit the u3-autorun.ini and change the name of the app you want it to load on insert.
There you go...a U3 Enabled device without the slow and bloated u3 software. enjoy!
(anyone who has any suggestions on how to make this much easier to read/do please post your suggestion and i shall do them.)
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
I don't know about the other files you mentioned, but the file Windows looks at for AutoRun information (e.g. icon, label, action, etc.) is called
Autorun.inf, notAutorun.ini.If I ever get another U3 drive (I only have one, and I've disabled the U3 LaunchPad on it, but I've got to save it for some reason, I think some of you can understand ;))
~3D1T0R
the autorun.inf is on the cdrom part, but all it does is execute the u3-autorun.exe that is on the cdrom. the u3-autorun.ini is what u3-autorun.exe looks for and reads. when you edit the ini file you place the name (eg startportableapps.exe) and location relitive to the ini file in the u3-autorun.ini
remember the autorun.inf is a different file completely from the u3-autorun.ini.
there you should be editing the autorun.inf, not the autorun.ini.
Also if you want to be able to use the regular AutoRun system on an un-updated system, or change the icon and/or label of the regular USB Mass Storage part, you edit the autorun.inf (again, not .ini) on that partition.
I have no knowledge of whether the others are .ini's or .inf's, thus for now, I'll assume you're correct regarding them (though I would suggest that you check and make sure, just to be safe).
~3D1T0R
i didnt spell the file name properly in that part of the tutorial, my bad....i will edit it and fix. thanks for the catch.
as for the using autoplay on the mass storage system, there are posts that have detailed that microsoft has disabled the additional entries for it here
I know about the update which disables AutoRun, and it's not installed on any of my computers, also a couple of my computers exhibit some strange behavior which causes CD drives not to AutoRun/AutoPlay, thus if I replaced the U3 LaunchPad, I personally would still want to have the AutoRun.inf on the USB Mass Storage partition edited so as to be able to start the Platform from that if the host computer supports it.
~3D1T0R
i was thinking that all we were talking about was the u3-autorun.exe itself not what windows does to mass storage devices, and that i didnt know that having an autorun.inf in the root of a mass storage device would allow it to have the extra options for autoplay.
it was my understanding that you saying that the u3-autorun.ini file is suppose to be the autorun.inf on the mass storage device part, which it is not. i do have both the autorun.inf and the u3-autorun.ini files on my mass storage partition but the only reason i have the autorun.inf was so that i could name/iconize that part of my device.
now my cdrom partition does have an autorun.inf for some of the same purposes, but all it starts is the "u3-autorun.exe" program. its the only thing on that partition besides the icon file and the autorun.inf. now u3-autorun.exe copies itself to a temp directory, searches the root of all devices for the file called "u3-autorun.ini" and then executes the file named in there. u3-autorun.exe then exits and removes itself from the host computer.
i know this may be redundant, but i wasnt sure if i had made it clear what the u3-autorun program did.
Thank you very much!
You do not know how you helped myself!!!
Thank you so much!
On the net, searched all forums, but this tutorial is only that things went well.
YOU ARE THE GREATEST!
Heh, i even refer to my own tutorial to fix the cdrom part of my u3 drive...
I'm not sure why you're replying to a long-dead topic. It bumps it to the top of the recent posts list without adding to it. U3 is *long* dead at this point and it's likely most of the drives have been tossed by now.
Sometimes, the impossible can become possible, if you're awesome!