Page 1 of 1

Invalid Opcodes message finally solved

Posted: Tue Mar 24, 2009 3:29 pm
by Icecube
Good news!

I don't get "Invalid opcodes" with memdisk anymore :D !

It was a simple fix. Just adding the raw parameter to memdisk. It was because of the fact that the image did work on certain PCs an not on other ones that I didn't thought about it (not mentioned in the memdisk documentation). Thanks to Erwan (syslinux) for reminding me to the raw parameter.
KERNEL /boot/syslinux/memdisk raw
APPEND initrd=/ubcd/images/fdubcd.igz
It would be great if someone who did get the invalid opcodes message, can confirm this.

Posted: Wed Mar 25, 2009 7:17 am
by procyon
On two machines i tested with the raw string and it worked.

The machines are relatively recent, HP Pavilion something, P4 and a generic crappy pc with an asus mb.

Posted: Fri Mar 27, 2009 8:47 am
by alm
Just tested it on one machine (ASUS K8VE-XE mainboard, VIA K8T890 chipset, AMD Sempron64 3400+). Adding the raw option solved both the invalid opcode error (option 1, 2, 6) and the hang after loading the CD-ROM driver (option 5).

Posted: Sat Mar 28, 2009 4:22 am
by Icecube
Thanks for confirming this 'raw' solution :D.

Posted: Fri May 29, 2009 9:19 am
by videonerd
Hi, I'm getting the invalid opcodes on my Panasonic CF-30. Parted Magic works fine, however.

n00b question here... where do we put in the RAW parameter? I have the ISO open with MagicISO.

Thanks!

Posted: Sun May 31, 2009 12:30 pm
by Icecube
When you boot the original iso, go to the menu entry that you want to boot and press <TAB> and add raw' (without quotes) to the command line that you see and press <ENTER>.

Or if you want to reburn the disk, extract the iso with 7zip and go to /ubcd/menus/syslinux/ and edit all config files.
Add raw to each APPEND line on which you find /ubcd/images/fdubcd.igz.
Rebuild the iso with the ubcd2iso script (/ubcd/tools/ubcd2iso/ubcd2iso.cmd) (follow instructions).

Or just have some patience until the next release of UBCD :lol: .

Posted: Sun May 31, 2009 1:15 pm
by videonerd
Thank you!! All that only to find out XOSL doesn't work properly (or refuses to work) on the laptop. SATA issue?

Memdisk documentation obsoleted by wiki

Posted: Fri Jun 05, 2009 12:02 pm
by Yet Another Smith
I guess the memdisk documentation should include a link to the MEMDISK Wiki.

I don't see any memdisk changes since 3.75 that might make raw unecessary.

Has anyone tried or found a need for the newest workaround bigraw ? (added in 3.08)

--- and thank you for making UBCD!!!

Posted: Tue Jun 16, 2009 7:42 am
by delicatepc
Using UBCD 5.0b12 USB (several usb sticks).

Machine is Lenovo X61. Updated to latest BIOS.

When ever I attempt to boot the FreeDos 1.33 I get the invalid Opcode at: 0003 0001 0202 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000

I have tried both the raw addition and the bigraw addition and it always fails with the same Opcode

Code: Select all

LABEL -
MENU LABEL UBCD FreeDOS R1.33 (Based on NwDsk V3.40)
TEXT HELP
 FreeDOS boot disk used to run many of the other DOS apps on the UBCD. Revised
 version of Eric Veermans' FreeDOS NwDsk 3.42. Addresses many bug fixes,
 performance enhancements and compatibility issues.
ENDTEXT
KERNEL /boot/syslinux/memdisk bigraw 
APPEND initrd=/ubcd/images/fdubcd.igz
or

Code: Select all

LABEL -
MENU LABEL UBCD FreeDOS R1.33 (Based on NwDsk V3.40)
TEXT HELP
 FreeDOS boot disk used to run many of the other DOS apps on the UBCD. Revised
 version of Eric Veermans' FreeDOS NwDsk 3.42. Addresses many bug fixes,
 performance enhancements and compatibility issues.
ENDTEXT
KERNEL /boot/syslinux/memdisk raw 
APPEND initrd=/ubcd/images/fdubcd.igz
Ideas?

EDIT: Just tested same USB stick and ubcd install on a Toshiba Tecra M7 and it is working like a champ on the M7 (freedos is booting as well as other applications). On the Lenovo X61 I could not boot Freedos nor the Drive Fitness Test or the Seagate Disk Test tools (those would just sit at init disk). Perhaps need to upgrade the syslinux and mem kernel?

EDIT 2: It seems that Lenovo machines have a real hard time with the floppy emulation. Does anyone have a idea why this may be? Is there something I could do to help pinpoint why?

Posted: Thu Jun 18, 2009 1:54 am
by Icecube
Can you boot this entries from the grub4dos menu?

Posted: Mon Jul 27, 2009 9:04 am
by delicatepc
http://www.boot-land.net/forums/index.p ... topic=8543

regarding the memdisk issues with lenovos i was experiencing...

I have opened a topic on the boot-land forums as it seems to a wider audience for memdisk issues.

One of the posters there mentions that it is currently a known issue and says that grub floppy emulation will work.

I was wondering if there was a way to directly load grub+floppy image desired from syslinux menu - I really want to avoid 2 menus for one off images.

Thank you,
dpc

Posted: Mon Jul 27, 2009 9:27 am
by Icecube
Post to the Syslinux mailing list: http://www.zytor.com/mailman/listinfo/syslinux or go to the Syslinux IRC channel: irc://irc.freenode.net#syslinux.

Describe the problem (on which models does it fail), which solutions you tried, that grub4dos emulation works.

Did you try the last MEMDISK already?
http://www.kernel.org/pub/linux/utils/b ... x/Testing/

Posted: Tue Aug 04, 2009 4:12 am
by Icecube
delicatepc problem is solved in Syslinux-3.83-pre6.
See: http://www.boot-land.net/forums/index.p ... topic=8543 for more details.

Posted: Fri Aug 21, 2009 6:10 pm
by heinzi
Hi friends,

i have still the problem that i get the opcode error when I try to boot my Lenovo X61 via PXE. I tried already memdisk 3.83-pre6 and pre-8 with raw and bigraw option and without any option.

Further I use the e1000.imz image from unattended-4.8 but tried already undis3c too.

Could somebody send me a working floppy image, because I am not sure whether the problem is caused by a wrong image.

Thank you very much in advance

Posted: Sat Mar 06, 2010 8:01 am
by Icecube
@heinzi
Try with MEMDISK of Syslinux 3.85

Re: Invalid Opcodes message finally solved

Posted: Sun Oct 24, 2010 11:15 pm
by andrewz
Icecube wrote:Good news!
I don't get "Invalid opcodes" with memdisk anymore :D !
How t ocreate memdisk ?
o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9
o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9
o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9
o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9
o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9
o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9
o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9o9
o9o9o9o9o9o9o9o9o9o9o9o9o9
инфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфо
инфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфо
инфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфо
инфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфо
инфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфо
инфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфо
инфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфо
инфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфо
инфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфоинфо