Jump to content











Photo
- - - - -

FreeDOS 1.2 and error JemmEx: exception 06


  • Please log in to reply
7 replies to this topic

#1 abpp

abpp
  • Members
  • 5 posts
  •  
    United States

Posted 18 May 2018 - 04:07 PM

I just installed FD 1.2 in an old Dell D610 laptop and the installation went well, but I am getting this old error:

 

 JemmEx: exception 06 occured at CS:EIP=12E5:0000D1D1, ERRC=00000000
     SS:ESP=12E5:000001F4 EBP=00000001 EFL=00033A47 CR0=80000011 CR2=00000000
     EAX=00000006 EBX=0000000F ECX:00000000 EDX=0000090D ESI=00000000 EDI=00000000
     DS=090D ES=029B FS=0030 GS=0010 [CS:IP]=FF FF 0F FF FF FF 0F 8B
     Press ESC to abort program
 
 
Which I did, and then this popped up right underneath the other thing:
 
 
     Bad or missing Command Interpreter: C:\FDOS\BIN\COMMAND.COM C:\FDOS\BIN /E:1024
     /P=C:\AUTOEXEC.BAT
       Enter the full shell command line:
 
 
I have no clue what happened. I wish I did. Any help would be GREATLY appreciated.


#2 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14323 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 18 May 2018 - 04:35 PM

 

I just installed FD 1.2 in an old Dell D610 laptop and the installation went well, but I am getting this old error:

 

 JemmEx: exception 06 occured at CS:EIP=12E5:0000D1D1, ERRC=00000000
     SS:ESP=12E5:000001F4 EBP=00000001 EFL=00033A47 CR0=80000011 CR2=00000000
     EAX=00000006 EBX=0000000F ECX:00000000 EDX=0000090D ESI=00000000 EDI=00000000
     DS=090D ES=029B FS=0030 GS=0010 [CS:IP]=FF FF 0F FF FF FF 0F 8B
     Press ESC to abort program
 
 
Which I did, and then this popped up right underneath the other thing:
 
 
     Bad or missing Command Interpreter: C:\FDOS\BIN\COMMAND.COM C:\FDOS\BIN /E:1024
     /P=C:\AUTOEXEC.BAT
       Enter the full shell command line:
 
 
I have no clue what happened. I wish I did. Any help would be GREATLY appreciated.

 

 

Hmmm. :dubbio:

 

https://www.mail-arc...t/msg12575.html

 

The probability that two users have the same error is very high, but the probability that two users would use EXACTLY the SAME wording to describe the error is so looow that, feeding it to the starship's Improbability Drive, the Heart of Gold could cross the universe, twice. :whistling:

 

 

:duff:

Wonko



#3 AnonVendetta

AnonVendetta

    Silver Member

  • Advanced user
  • 655 posts
  • Location:A new beginning.....
  • Interests:Self-development, computing

Posted 19 May 2018 - 12:25 AM

While the posts are similar, they are not verbatim word for word. And while it's true that plagiarists will oftentimes change up the wording just enough, I really don't see what motivation a user here would have for plagiarizing the words of a SourceForge mailing list user from 2012. What would they gain? I find this to be a matter of coincidence. Wonko, you have essentially made an accusation without stating it directly, and this is unjustified.



#4 abpp

abpp
  • Members
  • 5 posts
  •  
    United States

Posted 19 May 2018 - 07:00 AM

Guys, my error does not have exactly the same codes but is the same error. I copied from the 2012 posing because I had no way to copy/paste it from FreeDOS at the time. So, do any of you know how to solve this issue or not?



#5 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14323 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 19 May 2018 - 07:24 AM

Ok, you are "real", good :).

 

(you have no idea of the number of bots that just paste something they found on the internet creating a thread that will be later filled with spam, sorry if I doubted about your post being a real one).

 

The issue is likely in Jemmex, as detailed in the answer by Eric Auer :worship: :

https://www.mail-arc...t/msg12579.html

 

Can you access (via floppy, USB or *whatever*) the volume where you installed the FreeDOS?

 

Try to (temporarily) rename autoexec.bat and fdconfig.sys to *something else* and see if the system boots without loading anything "fancy".

 

You might need to put a copy of C:\FDOS\BIN\COMMAND.COM in the root of the volume (i.e. C:\COMMAND.COM).

 

DELL systems - generally speaking - are known to have some "queer" behaviour not only with FreeDOS but also with a number of other OS's, but they are not the "only" hardware having issues with JEMMEX, if the system without loading anything else boots, then you can try the solutions suggested here (or you can try using them directly, the test without any drivers/other things loaded is only to see if there is any *other* issue with the install):

http://wiki.freedos....ualBox_-_JEMMEX

 

@WhateverIsYourNameToday

The post as been copied and (partially) pasted, verbatim, word for word:

 

 

Which I did, and then this popped up right underneath the other thing:

Bad or missing Command Interpreter:
C:\FDOS\BIN\COMMAND.COMC:\FDOS\BIN /E:1024
/P=C:\AUTOEXEC.BAT
Enter the full shell command line:


I have no clue what happened. I wish I did. Any help would be GREATLY
appreciated.

including the CAPITALIZATION of GREATLY.

That the copy/paste has been done in good faith and by a "real" user having a "real" problem is another thing.

 

:duff:

Wonko


  • abpp likes this

#6 abpp

abpp
  • Members
  • 5 posts
  •  
    United States

Posted 22 May 2018 - 03:54 AM

Thanks, Wonko. I will try all that and let you know.



#7 Blackcrack

Blackcrack

    Frequent Member

  • Advanced user
  • 369 posts
  •  
    Germany

Posted 28 May 2018 - 07:42 PM

Hi Blacky

  I do not have a login to that discussion board, so maybe you can copy-and-paste this answer for me?
The error comes from JEMM386, and can be solved using /NOINVLPG to avoid using the INVLPG opcode. That's what is hanging up this user. On physical hardware, invalid opcode usually comes from AHCI in the BIOS, and the solution is usually to use legacy IDE. Check if your VirtualBox is emulating AHCI in the BIOS, and if you can change it.
After install, you have an option to load FreeDOS without drivers, to see if JEMM386 is the problem. Instead, you could try pressing F8 when the FreeDOS installer boots. F8 will let you trace CONFIG.SYS and AUTOEXEC.BAT. Or you could press F5 to skip CONFIG/AUTOEXEC entirely. The CDROM installer should(?) still work without CONFIG.SYS, but I think you'd want to run AUTOEXEC after you get to a command prompt, so it can set the environment variables needed for the install.
An alternative solution I've seen mentioned elsewhere is adding the raw parameter to memdisk in the boot menu.
When you boot the FreeDOS install CDROM, when you get the get the first "Welcome to FreeDOS 1.2" boot menu, press Tab when you're on "Install to harddisk" and add 'raw' (without quotes) to the kernel command line, then press Enter to boot.

From this:
KERNEL /boot/syslinux/memdisk

To this:
KERNEL /boot/syslinux/memdisk raw


 

On Tue, May 22, 2018 at 12:56 AM, Blackcrack <blackcrack@xxxxxxxxxxx.xx> wrote:
--------------------------------------------------------------------------------
Hi Jim,

if you want :
http://reboot.pro/to...x-exception-06/

best regards
Blacky



#8 abpp

abpp
  • Members
  • 5 posts
  •  
    United States

Posted 29 May 2018 - 05:03 PM

"Blacky"?? Ok...  :mellow:
 
Yes, this is in real hardware (old Dell D610 laptop).
 
I will try your 'raw' option too...
 
 
 
 

Hi Blacky

I do not have a login to that discussion board, so maybe you can copy-and-paste this answer for me?
The error comes from JEMM386, and can be solved using /NOINVLPG to avoid using the INVLPG opcode. That's what is hanging up this user. On physical hardware, invalid opcode usually comes from AHCI in the BIOS, and the solution is usually to use legacy IDE. Check if your VirtualBox is emulating AHCI in the BIOS, and if you can change it.
After install, you have an option to load FreeDOS without drivers, to see if JEMM386 is the problem. Instead, you could try pressing F8 when the FreeDOS installer boots. F8 will let you trace CONFIG.SYS and AUTOEXEC.BAT. Or you could press F5 to skip CONFIG/AUTOEXEC entirely. The CDROM installer should(?) still work without CONFIG.SYS, but I think you'd want to run AUTOEXEC after you get to a command prompt, so it can set the environment variables needed for the install.
An alternative solution I've seen mentioned elsewhere is adding the raw parameter to memdisk in the boot menu.
When you boot the FreeDOS install CDROM, when you get the get the first "Welcome to FreeDOS 1.2" boot menu, press Tab when you're on "Install to harddisk" and add 'raw' (without quotes) to the kernel command line, then press Enter to boot.

From this:
KERNEL /boot/syslinux/memdisk

To this:
KERNEL /boot/syslinux/memdisk raw
 

 

 

 

 

On Tue, May 22, 2018 at 12:56 AM, Blackcrack <blackcrack@xxxxxxxxxxx.xx> wrote:

Hi Jim,

if you want :
http://reboot.pro/to...x-exception-06/

best regards
Blacky






1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users