I have an HP ProLiant N40L MicroServer that needed its BIOS upgraded. I downloaded the proper firmware update package from HP’s support site which includes ROMPaq and the update flat files. I created a bootable USB thumbdrive using the ROMPaq utility, however attempting to update the server’s BIOS receives this error:
RomPaq may take a few minutes to get started, please be patient... Command or filename not recognized
Open the SWSetup folder that the ROMPaq installer creates and copy all files from the “Flat Files” folder over to the USB drive that the ROMPaq utility modifies to be bootable.
The Long Story
After the “Command or filename not recognized” error was received, I popped the USB drive into a different machine and inspected the contents. Looking at the AUTOEXEC.BAT file that is on the root showed this:
@echo off echo ROMPAQ may take a few minutes to get started. Please be patient... rompaq.exe /l:us /!
However, there was no rompaq.exe file anywhere on the drive! Furthermore, there wasn’t even a ROM file to be seen. Clearly the utility did not create a drive that was capable of flashing my server. Part of the unpacked files included a folder called “Flat Files” that included things which made more sense. For example, in that flat files folder was an AUTOEXEC.BAT file that looked like this:
@echo off if errorlevel == 1 goto ENDIT if errorlevel == 0 goto other :other echo Next Please!!! flash.bat :ENDIT
As well as a flash.bat file that looked like this:
kbd /"flash O41072~1.rom -r 100000,10000 -r 1e0000,10000;q"
And finally an actual ROM file that matched filenames with the line in the flash.bat file. I merely copied all the files in the “Flat Files” folder over to the USB key and chose to replace any existing files.
Apparently HP’s QA group let this get past them. The tool and documentation explicitly state that it will, once run, leave the USB media in a state that can be used to directory update the ProLiant firmware. No additional steps should be needed, according to the documentation. That is clearly not the case in this scenario.
Ever had a similar experience with ROMPaq or is this an oddball case? Let me know in the comments.