Smi Mass Production Tool Setting Password
Mine had a SM3267ABS controller, which wasn't supported by the SMI tool linked in step 4. A bit of Googling led me to SMI Mass Production Tool V2.5.36, which is a newer version of the one you linked. Amendment to step 5: I had to hit the 'Scan USB (F5)' button first.
1000 is a common PID which is used as a default PID by these programming tools - it implies that you or someone else has used a tool to re-program the firmware at some time and lost the original PID.? I have only done numerous attempts with SMIUFDiskUtilities and a few RmPrepUsb. Use nirsoft USBDeView to list all devices that were and are connected to your system - maybe one of these will be the original VID/PID of the USB flash drives? Look for a Class 8 SubClass 6 device. Will do when I get home tonight! I've been looking in Windows 7's Device Manager device properties so far. Use nirsoft USBDeView to list all devices that were and are connected to your system - maybe one of these will be the original VID/PID of the USB flash drives?
Look for a Class 8 SubClass 6 device. I have searched all round my different machines running USBDeview but all I find is the 090c/1000 ids for both sticks. Here's data for one of the sticks: Port#0007.Hub#0005 SMI USB DISK USB Device Mass Storage No Yes No No 0-01-10 13:-01-10 20:58:32 090c 1000 30.00 08 06 50 USBSTOR USB Mass Storage Driver USBSTOR.SYS USB Compatible USB storage device 2.00 USB Mass Storage Device 6.1.7601.17577 USB VID090C&PID10600000483 I can only assume the sticks were this way when I bought them. Is it the made-up ProductId that stops me from creating a correct CD partition? How do these pieces fit together and what can I do? This is interesting.
I ran sm32Xtest.exe from (which seems to be SMI's mptool v1.17.13) and clicked 'Scan USB', which resulted in:. 0 MB reported for both USB sticks. opening the device properties shows garbled information. the 4GB stick triggers some retry behaviour and gets unmounted and mounted repeatedly as long as the mptool is running Then I tried with SMI's mptool v2.03.58 that I had previously downloaded. It works much better:. correct MB reported.
device properties shows correct information This makes me wonder if I have some new version of the SMI chip not supported by the older tools, and creating the CD partition may work with a newer version of the UfDiskUtilities? Or can I do this with the mptool?
(BTW: is there an easy way to upload screenshots to forum posts?). Click on Scan - then double-click on the entry displayed on the main window and click on Save Info) - also take a screen capture of this form.
Click on Settings and choose a default.ini - you will then see the settings form. All the info in this will be wrong. You will need to change the fields to match what is reported by ChipGenius (take a screengrab of chipgenious and save the file so you have it safe).
Set the inf and click Save to File - choose a name like Lexar001.ini. 'Other Setting' will allow you to set a CDROM portion and a secure hidden (Security Disk) area if you wish. I have not personally used this tool and I was going to experiment this afternoon on one of my 2GB lexar jumpdrives to test it out. Ok, so we're in research mode:-) So basically assign everything we know and let the rest stay at their defaults until proven otherwise?
Smi Mass Production Tool Setting Password
I found CD mentioned in two places: 1) Main tab Make Auto Run (can specify.iso) 2) Multi-lun Setting tab uDisk partitions Static CDROM Size I wonder if (2) is a different kind of CD, or just a way to ask for a fixed size 'Auto Run' partition? It would be great to have a static CD partition where you could swap.iso file without destroying the other data on the stick? If you're about to do some tests I might wait to hear about your experiences, there's a LOT of settings:-). This is the drive i flashed using one of the two tools mentioned above I made no changes to any files on the tool and followed a translated page from flashboots.ru forum on the one I used. Sorry I cant define which one it was, it was about 4 yrs ago. If you're about to do some tests I might wait to hear about your experiences, there's a LOT of settings:-) OK - just trashed my Lexar 2GB! I found 4 versions of the MP tool (all similar names) - 2 appeared to detect the Lexar.
I used the latest version of that one and reformatted using an autorun entry and the test ISO that came in the zip file (which just has autoruns.exe and autoruns.inf). This appeared to work and I had two devices (a 720MB flash drive and a small CD-ROM.
I then wanted to set the device back so I re-ran the app and this time it detected two devicesd in two ports (1 and 3). I unticked the autoruns checkbox and re-ran the utility - now it is not detected by Windows! If I insert it into any computer, Windows makes a USB-inserted 'ding' noise but no device appears in Disk Manager and there is a bang in Dev Manager! - trashed Maybe best not to use the autoruns/cdrom setting on these tools! I have another 2GB and may try experimenting with that one tomorrow - if I have the nerve!
Official Sites: Mot Password = 123.or.Without Password Software Controller Part-Number SM323. SM321 SM3252. SM32XX SM32x (SM321AC. SM3251BA (VID=0325 PID=AC02, VID=1B1C PID=1AB1) SM32x SM32x (VID 0325, VID 0324, VID 0321, VID 090c) (VID 125F PID 385A, VID 125f PID b042) SM321, SM324, SM325 SM3255AA SM325AC. SM3252C SM32x.
SM3252C SM3211BC. SM3211BC1 SM3255. SM3254 SM32x. SM325AC SM32x.
SM3251BA SM32x. SM340AB (VID=090C PID=1000) SM3255AB SM3257. SM3257AA SM32XX. SM321CC SM3254AE SM3211BC1. SM3211 SM3254 SM3211.
SM3211BC SM3252A. SM341BA SM3255ENA1. SM3255ENAA SM3252G. SM3257AA SM3257EN SM3211.
SM3255 SM3257 SM3257. SM3257ENAA SM3211BC.
SM3211BC1 SM3255TS SM3255AA. SM3255AB SM3257. SM3267 SM3254AE. SM3267AB SM3257ENBA. SM3257ENAA SM3257. SM3257ENAA SM321AC.
SM324BC. USB Software.