wavefullpac

Xpadder will simulate keypresses and mouse movements using a gamepad.

1. How To Extract Rar File In Asp.net C#

I have started this thread to ask for a little help from or anyone with an Asmedia 104x USB 3.0 chip. I have located a 130704100201 firmware in a.ffs module and I'm trying to see if it can be extracted for flashing. This may seem impossible, since the stand-alone firmware has a custom 5 bytes checksum for CFG table and another 5 bytes checksum for the body, while the embedded firmware has none. But I want to see if it there is a way to avoid this. Download and put the content on a bootable DOS USB. You can then run from the prompt command:104xfwdl /?- for a list of commands104xfwdl /D- for current firmware and SSID/SVID104xfwdl /A- the most important, for backing up current firmware. Upload this here, with the info from /D command.

Users with programmer and clamps can also try to read some chips around the Asmedia controller and upload them for inspection, if the /A switch fails.I won't ask anyone to flash this extracted firmware, since it has some risks. In fact, I will provide the newest stand-alone firmware, version 131025101103, for those who just want the original stuff. A warning though: this was released for a RocketU external card. In theory it should work for any 104x chip and should also be easily reverted to older versions, but the practice is a different thing. Users should modify 104xfw.cfg with their corresponding SVID/SSID.I don't have any Asmedia chip to test this and it is only for tinkering. Torrent ulead photo express ita.

I don't expect/offer any important result, so neither should you.EDIT by Fernando: Thread title customized to be able to merge all existing posts regarding this topic. Hmm, I flashed the new firmware successfully. But when I verified it told me that I'm on FW 1008300000d now. The controller works in DOS environment but not under Windows anymore. Coming to think of it I think I had this problem with the 13x FW from station drivers a couple of weeks ago already. I'm not sure how I solved it (flashing back my backup was not possible) but I investigate;-)Best regards hansonEDIT:On this picture you can see the errror I get. Do you think it has something to do with the filesize (it's double from the size of the file that came with the downloadable FW).

You need to edit 104xfw.cfg with the following: remove // from NEWFILE, SVID, SSID, then edit with NEWFILE=1; SVID=0x1849; SSID=1042. Are you sure that your chip is 1849&1042, since normally should be 1B21&1042? What does device manager shows?I have checked the dump and it is the same as original bin + padding. This is how it looks when comparing with a similar firmware from another ffs, meaning stand-alone vs embedded in BIOS:I know that the checksum is 5 bytes, because this is how it looks with custom 104xfw.cfgEven if I copy the header from another firmware, since it is just CFG table, I still have to add a checksum to the body:I can patch the 104xfwdl.exe to ignore the checksum and flash as it is, but I don't know who would test this kind of stuff. Anyway, a newer and original firmware is available, so nothing is lost.

Thanks for all your testing, even though I don't say this all the time. I hope you will also let me know on the UEFI VBIOS for GTX680. If you try with custom.cfg and it still fails, then here is original 120816 firmware to be flashed from Windows.If you get problems because of different SVID/SSID, even though it shouldn't happen, copy the.bin to the 130201 or 131025 folder, alter 104xfw.cfg with the values I told you, edit u.bat with the name of the bin, in this case xHCIv12081602026D.bin, then flash from DOS.All 13xxxx firmware come from external cards with 4 USB ports, so maybe this is the problem. But I still advise you to try with custom.cfg. I have found new things. This is how the header is formed:The CFG table is different between onboard and external, also the signature.

The CFG table is the same for all similar devices, onboard has one and external has another. After the body size comes the body and the footer:I have found a 130125000200 firmware that is similar to 11xxxx and 12xxxx branches. I think this has 90% chances of working for you, maybe editing 104xfw.cfg is required.I have also added the onboard CFG table to the latest 131025 firmware. Flash at your own risk. The interesting thing is that the 130704 firmware from Asus mainboard BIOS has the same structure as 130201 and 131025, which makes me think that the CFG table has an important part.Edited: Asmediaasm104x131025mod.rar was removed because it was bricking the controller. This should be my fault, since I didn't explicitly wrote that you must first probe the chip with a programmer, to be sure of reverting even in case of misflash.

I just thought you will do it anyway and I also thought that it shouldn't be that hard to downgrade. Anyway, I hope you still have some working ports, since the specifications of your mainboard tell that only the front ports are handled by Asmedia.It is sad that this happened, since I just got to the rest of unknown bytes:The header is common for all onboard devices:But the external cards have a different header:That is why I thought it might be easy to just port the header from older firmware. The firmware 130704, which was found in Rampage IV mainboard BIOS, has a similar structure with 131025 and I again thought it is just a matter of right CFG Table. Someone knows if Rampage has some extra features that might make them to work with the same firmware as external cards?Back to your problem. You should probably try with your programmer and some clamps, maybe it will detect the chip. By looking at, I would say that the Asmedia controller is at the bottom and the chip under it.

The datasheet for the chip is.But better start with the flashers I attached. Unrar to a bootable USB and run from DOS prompt: testDOS or testDOS.batSee if it detects anything from the chip. It will loop trough all the folders and run some commands, so better be patient and watch the screen, press any key when asked. If no sign of life, use the same folder from Windows and run testWIN.batNext stop is with Bus Pirate. Make sure you have the latest firmware for it, then download the flashrom attached, which should work from Windows.

Cut power from the mainboard, attach the Bus Pirate to another system and check the COM port (example from ), then connect to the chip. Connect like in and the datasheet of the chip, read the options.Open a command prompt from the folder containing the attached flashrom and type:flashrom -h (for help)flashrom -p buspiratespi:dev=COMxx -r asm1042.rom (to read the chip, where COMxx is the port, like COM8, COM13.)- if the reading goes well and the dump is the same as the flashed 131025mod.bin + padding, then go ahead with the next command, otherwise post here with results.flashrom -p buspiratespi:dev=COMxx -w DE0026D.BIN (to flash the backup bin, which should be in the same folder as flashrom. Then flash from DOS to 130125)Hope this helps. No need to worry.

How To Extract Rar File In Asp.net C#

It's just front usb as you already found out. And so I get some skills with my bus pirate;-). I managed to get it working already (the hint with specifying the com-port was what I needed). Tomorrow I will move my secondary PC in front and try some flashing. Your ASMedia flasher did not work unfortuntately but I have the feeling that I'll manage it by bus pirate and report straight after.Best regards hansonEDIT: I made several tests with the BP and different SPI's I had at home. All works great and as it should.

If the MXIC chip is supported I will habe success for sure;-). By the way, do you have a newer 'flashrom for windows' available? I updated my FW to version 6.3 (which is the latest) but the flashrom release seems to be a bit out of date.Best regards hanson. It is easy for me to overlook the risk, when it is not my hardware in line. I hope you won't keep something against me for this foolish dreaming of easy modding. I still don't understand why manufacturers don't provide a more reliable method of identifying controllers in case of a bad flash.

If you want to have something to play until you flash the chip:- download again the package from and rename libusb0x86.dll to libusb0.dll. I previously uploaded a newer libusb0.dll, maybe it had problems. You can even get libusb0 from and install the x86 filter. Connect the Bus Pirate and run from flashrom's folder:flashromflashrom -p buspiratespi:dev=COMxxDoes the chip gets detected?- you probably used some clamps for connecting the Bus Pirate, so why not do the same with your EZP programmer?- maybe you will have better luck from Linux, since you can?Again, this is not a solution, just something to try when you are bored. The harm is already done.