Can someone kindly post a link in rapidshare.com or Megauplaod for Latitude D630 ver. A16 SLIC 2.1? I can't download from Raipshare.de. Thanks in advance.
1537 mod is not working hi there, I tried the other version of 1537 mod by vtrash, and both of them are not working, still showing 2.0 i wish to extract BIOS ROM out of the 1537_A09.EXE, but using -writeromfile under CMD does not working, it says unknown parameter etc.... how do i get a 1537 clean ROM plz...
Try to read on second post in this thread about n-series. Starts with "Posted by kerimcem about the Dell n-series free-dos PC's" To extract rom you can try to use key /WriteRomFile or extract with help of WinHex 4 rar files. Search for "Rar!" and copy content from "R" until file end into separated rar file. Then extract this file with rar archiver. !!! There are 4 "Rar!" entries. Repeat for each one. Does you bought PC with Windows or Unix? Please provide results here.
Thank you for the replay. Yes, I did what you said.. how to extract files from that EXE file. (of course -writeromfile or /writeromfile does not work for 1537_A09.EXE) starting from Rar! -- "R" till the end, copy to into new file, save as .rar, and extract it. I got 4 folders/files 1) WinPhlash1696 folder ... I believe it is the 32 bit flasher 2) flashabl.rom size 2088kb looks like it is the ROM file I am looking for? 3) flashabl.rom size 1kb .... im sure i did it correctly and tried 3 times, but still, does not look right as the size is too small? 4) WinPhlash64 folder..... the 64 bit winflasher Are the results correct to you? I got this DELL Studio 1537 with Vista Home Premium on it... currently BIOS A08
BTW, I do not understand why you want me to read the second post starting with "Posted by kerimcem about the Dell n-series free-dos PC's". They seems talking about how to flash under DOS, do you want me to try flash under DOS instead of under Windows?
That's right. rom from 3) is samething special. I do not know that is it. May be additional header? like hdr? Anyway extraction is ok. rom from 2) is right one. If you will compare it with my modded rom then the difference extract only in slic. I do not have any ideas why this area is not written. You can open rom with PBE and see correct slic in hole09.rom. In original rom that 2.0 in modded 2.1. All other areas are not changed. Extraction of rom see in the PBE/Temp dir. You didn't answer my questiion. Have you initially laptop with preinstalled windows or unix? May be your slic is hidden. Theoretically you can try to flash with dos flasher. May be original 1537_A09.EXE does something special by or before flashing.
Hi vtrash, thanks for the reply again. My laptop intially is with pre-installed Windows Vista Home Premium. Last night I used 'UltraCompare' tool to check your first edition mod bios and the original bios I extracted. You are absolutely right that only the SLIC field has been changed. There is only 157 bytes differences in those two files. And yes, there are lot more changes if I compare with the second mod version. I will do a bit more research and see what I can do. Btw, I have few more questions for you. 1) how do I know if my SLIC is hidden or not. I think mine should be normal, as I can see under SLIC Dump TooKit, it says DELL M09, SLIC 2.0, and under Everest, Table length is 374 bytes. 2) When I use PBE to open the original bios I got, it says ' NO BCPs found'. I also tried to open your mod bios, same error message.... not sure why PBE is not allowing me to open it. I am using Pheonix BIOS Editor Pro, version 2.2.0.1. Actually, when I run PBE (under VISTA HP), a message pops up saying "you are running PBE under a DBCS OS which may cause unexpected errors. Continue? Y/N" and I clicked Y. Is that same for you? 3) those 4 folders/files make sense to me except the third 1kb one. I am wondering do you have confident on that method that starting with "RAR!" till the end of the EXE file to generate new RAR file. Not to offend, but I actually intentionally tried to start ONE bytes early than "RAR!" on the third one -- to start with "P", and guess what I got? The same folder as the fourth one. Instead of that 1kb file, I got the WinPhlash64 folder. Then I applied 'UltraCompare' to check each of the files under those two folders, they are identical. This confused me....why only one byte offsetting can generate such a huge difference? I hope you know what I am talking about.... Finally, I actually enjoyed with what I am doing, it feels very hi-tec. Thanks again for all the guides and hints.