Source code? Hi! Is the source code for this tool available somewhere (git/SVN/*.zip)? It is a bit troublesome for me to run this tool since I'm a Linux user. Secondly, releasing the source code might get other enthusiasts to contribute enhancements. Thanks!
Hi No, its not. I don't have the time to co-ordinate a community effort. Nor do I want to risk problems being introduced. When I no longer have the time to maintain it, then i'll happily release it. Its VB.NET 2010, not sure that's too helpful for Linux. Andy
HDR Checksum not correct A bit more info on my issue w/v1.93 and the Dell Optiplex 755 A17 BIOS file: I should have mentioned that I have successfully used the tool to create 2 other modded BIOS's. Since my first post, I have downloaded several different versions of the Optiplex 755 BIOS (going back as far as A08) and none of the file checksums hash to 0xFFFFFFFF (computed using WinHex). I've since downloaded perhaps a dozen random Dell BIOS files and in all other cases, the file checksum is 0xFFFFFFFF for the .HDR file. In this case, it appears Dell has changed the checksum calc for the Optiplex 755. Since others have reported successfully creating a modded O755 BIOS, I assume there is some trick (or Advanced option) to getting past the "HDR checksum not correct" error. Am I missing something obvious ?? Thanx for any replies...
AndyP - The Dell Inspiron 9300 BIOS was for me. I think the problem was that there wasn't enough space left and you had to overwrite an un-used table. krzychb - I still have AndyP's original hand-made one that's running on the laptop now. Let me know if you want me to upload.
Please do :L I'd love to see what inspiration I had I think we probably dispensed with the last SSDT table and nop'd out the line of code that added the address for that, that overwrote the SLIC address Andy
Andy & tqhoang - you guys are simply great willing to spend your time and effort to track down work done two years ago. I do really appreciate it - whatever you will finally find out.
I don't have access to the laptop yet, but here's the checksums/hashes of my A05I9300_SLICE.EXE. Let me know if yours are the same. Code: CRC32: 4f25dfa1 MD5: b307e16cbb56f9e4991db4c0353bd86a SHA-1: 5ea8e2af82dea0866634abe504d5726f211afe6e SHA-256: 6fedb2fbe979f2e03b16ddbfc627d41919742f4277da1cd382f5bec3d7374ace Also can you provide an RW-Everything report for your I9300 after you flashed the BIOS with your SLIC'ed EXE?
Which particular SLIC'ed EXE do you mean? I have flashed couple of BIOS mods: 1. prepared by myself with phoenixtool195 2. prepared by akcent and by Serg008 I could not find one matching your checksums/hashes
Ok, I just checked my backup USB hard drive and found an old A05I9300_SLIC.EXE (using Dell QA09) from March 22, 2010 and a matching RW-Everything report after the BIOS was flashed. This should be what is running on the Inspiron 9300. Also I just used the latest PT v1.95 and it generates the exact same A05I9300_SLIC.EXE. @krzychb - It appears the problem is the RW-Everything report that you posted is confusing the PT v1.95. What version was this?...v1.5.x? My working RW-Everything report is attached and is likely from v1.4.7 (was current at the time). If you use my report and the Dell M09 SLIC, then you can generate the identical EXE. @AndyP - Attached are two logs (working one using my v1.4.7 report and the non-working one from krzychb). Good luck to all!
I don't know if this is any use too BIOS modders, but I found the Windows API to modify NVRAM. Code: GetFirmwareEnvironmentVariable() SetFirmwareEnvironmentVariable()
Yes, it was the main reason for me to update my D630 to A18, because any idiot could find out master-password for my laptop from certain web-site. Had to cut off the "signature" and modify the rom manually, then flash from DOS and A17.exe