Bad command or firmware - "WIN1501263.EXE"
Gustavo Narea
me at gustavonarea.net
Thu Sep 4 18:36:32 CDT 2008
Hello, everyone.
I'm trying to upgrade my BIOS with biodisk, but it mounts an image which has
0% free space and then tries to write in it, so it fails. This is the output I
get:
> $ sudo biosdisk install Win1501263.EXE
> + mkdir -p /tmp/biosdisk
> + cp -f /usr/share/biosdisk/dosdisk.img /tmp/Win1501263.img
> + mount -t vfat /tmp/Win1501263.img /tmp/biosdisk -o loop
> + cp -f Win1501263.EXE /tmp/biosdisk
> cp: escribiendo «/tmp/biosdisk/Win1501263.EXE»: No hay espacio libre en el
> dispositivo + echo 'Win1501263.EXE '
> + unix2dos /tmp/biosdisk/autoexec.bat
> + umount /tmp/biosdisk
> + rm -rf /tmp/biosdisk
> + '[' '' == 1 ']'
> + '[' 0 == 1 ']'
> + '[' 0 == 0 ']'
> + echo 'Creating BIOS floppy image at /tmp/Win1501263.img'
> Creating BIOS floppy image at /tmp/Win1501263.img
> + '[' 1 == 1 ']'
> + install
> + local kernel=/boot/memdisk
> + '[' -z ']'
> ++ basename /tmp/Win1501263.img
> + title=Win1501263.img
> ++ dirname /tmp/Win1501263.img
> + '[' /tmp '!=' /boot ']'
> + cp -f /tmp/Win1501263.img /boot
> ++ basename /tmp/Win1501263.img
> + destination=/boot/Win1501263.img
> + /usr/sbin/blconf --title=Win1501263.img --add-kernel=/boot/memdisk
> --add-initrd=/boot/Win1501263.img + echo 'Copied image to
> /boot/Win1501263.img and updated bootloader' Copied image to
> /boot/Win1501263.img and updated bootloader
> + '[' 0 == 1 ']'
> + '[' 0 == 1 ']'
The error caused by `cp -f Win1501263.EXE /tmp/biosdisk' translates as
"writing «/tmp/biosdisk/Win1501263.EXE»: There is not enough space in the
device".
I get that error even with `mkimage'.
How can I fix this? Would this be solved if it's saved to a CD? If so, how can
I do it? I couldn't find information on how to do it in a CD.
I'm using Ubuntu Hardy.
Thanks in advance.
--
Gustavo Narea.
http://gustavonarea.net/
Get rid of unethical constraints! Switch to Freedomware:
http://softwareliberty.com/
More information about the firmware-tools-devel
mailing list