Does your BIOS come with a "Firmware Update" BIOS Boot Option? If it does, it should provide you a File Manager to select files from the USB drive and verify that the selected file is actually an applicable firmware update. Even if the file is just an EXE, the "Firmware Update" File Manager is smart enough to look into the file and extract the BIOS update.
On Mon, Jan 6, 2020 at 11:43 AM Jack Browning <[email protected]> wrote: > > I suspected as much. Dell support, of course, runs and hides when it comes to > any issue outside the Microsoft ecosystem. So, no joy there. > > Thanks for your time and prompt reply, Tom. > > On Mon, Jan 6, 2020 at 1:30 PM tom ehlert <[email protected]> wrote: >> >> Hallo Herr Jack Browning, >> >> am Montag, 6. Januar 2020 um 19:32 schrieben Sie: >> >> > I've been trying to update the BIOS on my wife's Dell Inspiron 17 >> > 5721 laptop using FreeDOS. I've tried to do this with FreeDOS 1.0, >> > 1.1, 1.2, and 1.3rc2, each time with the same result. >> >> >> > What happens is this: after setting up FreeDOS on a USB stick using >> > its .img file (and adding the BIOS executable, 3521A16.exe), I can >> > boot without incident into FreeDOS on the laptop. After opting not >> > to continue with the installation, the DOS prompt I'm dropped into >> > seems to be fully functional, i.e., all the builtin commands appear >> > to work normally. When I go to run the BIOS updater by typing the >> > .exe's file name and hitting return, however, the only thing that >> > happens is that the word "Test." is printed to the console. The >> > updater then exits without doing anything else. >> >> >> > The updater is what Dell describes as a "Universal (Windows/MS >> > DOS)" application. Even though it appears to the file system as a >> > single .exe file, it is actually a package, containing these files: >> >> >> > Ding.wav >> > FlsHook.exe >> > FlsHookDll.dll >> > FWUpdLcl.exe >> > InsydeFlash.exe >> > iscflash.dll >> > iscflash.sys >> > iscflashx64.sys >> > isflash.bin >> > platform.ini >> > xerces-c_2_7.dll >> >> >> > Frankly, I don't know enough about DOS to know whether this kind of >> > application structure is normal in a DOS environment. I'm just >> > mentioning it as a possible issue. >> >> this is definitively not a DOS application. >> most likely you are supposed to run (on Windows 10) recoverydrive.exe >> and run this stuff. anything else should go through the Dell support >> forum. >> >> >> >> > I've scanned for strings in all of the files of the updater, and >> > did not find a "Test." string, which leaves me with the question of >> > whether "Test." (and the premature installer exit) is coming from FreeDOS. >> no. >> >> >> more help should come from Dell support. >> >> Tom >> >> >> >> _______________________________________________ >> Freedos-user mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/freedos-user > > _______________________________________________ > Freedos-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/freedos-user _______________________________________________ Freedos-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-user
