SpinRite 6.1 RC3 - NumLock brings up "Attempt to Execute Illegal Opcode"

  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

    /Steve.
  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)

rhovdestad

New member
Nov 9, 2023
2
1
While running SpinRite 6.1 Release Candidate 3 I attempted to "resume" a level 3 scan on a drive. After selecting the drive, I pressed CTRL+Enter to go to the page allowing me to enter the starting point (in my case 72%). I typically use the numeric keypad for numbers, noticed "NumLock" was off, and pressed "NumLock" to enable the keypad.
Up popped the screen shown in the attachment.
 

Attachments

  • Image.jpg
    Image.jpg
    253.1 KB · Views: 148
Hi! I haven't been able to make this happen here. (Which is certainly not conclusive.)

So the first question is: Does this repeat for you? Does this occur every time to toggle NumLock ON while at that Starting/Finishing Locations screen?

Also, how did you prepare your boot media? I've recently posted the latest release candidate of the Windows boot prep tool. Could you:
  1. grab it from:
  2. run it to create (or recreate) your boot thumb drive,
  3. replace the unlicensed "SPINRITE.EXE" that it adds to the drive with your licensed copy of SpinRite,
  4. then boot that and see whether this still occurs?
THANK YOU!!
 
Hi Steve,

I was able to reproduce it every time with RC3.
I'm unable to reproduce in RC5.

Thank you for a great product!
 
  • Like
Reactions: Steve
". . . While running SpinRite 6.1 Release Candidate 3 I attempted to "resume" a level 3 scan on a drive. After selecting the drive, I pressed CTRL+Enter to go to the page allowing me to enter the starting point (in my case 72%). I typically use the numeric keypad for numbers, noticed "NumLock" was off, and pressed "NumLock" to enable the keypad. Up popped the screen shown in the attachment . . ." SRPR-RC3 Attempt to Execute Illegal Opcode! E1D0
". . . Hi! I haven't been able to make this happen here. (Which is certainly not conclusive.) So the first question is: Does this repeat for you? Does this occur every time to toggle NumLock ON while at that Starting/Finishing Locations screen? Also, how did you prepare your boot media? I've recently posted the latest release candidate of the Windows boot prep tool. Could you: 1. grab it from: https://www.grc.com/dev/SpinRite/WinSpin/SR61-R5.EXE 2. run it to create (or recreate) your boot thumb drive, 3. replace the unlicensed "SPINRITE.EXE" that it adds to the drive with your licensed copy of SpinRite, 4. then boot that and see whether this still occurs? THANK YOU!! . . ."
". . . Hi Steve, I was able to reproduce it every time with RC3. I'm unable to reproduce in RC5. Thank you for a great product! . . ."

Hi @rhovdestad,

". . . how did you prepare your boot media? . . ."

Is that resolution also with the same boot drive as previously used, only switching to SRPR-RC5 instead of SRPR-RC3, if so, how was that boot drive made, and what DOS and KERNEL.SYS ( if FreeDOS ) is on it?

Or was that resolution also with a 'fresh' boot drive made with SR61-R5, and then running SRPR-RC5 from there?

Thanks.
 
Last edited:
I was able to reproduce it every time with RC3.
I'm unable to reproduce in RC5.
THANK YOU for the confirmation feedback! MUCH appreciated. I was able to get it to fail once, but since I couldn't make it happen repeatedly I could never be certain that the problem was resolved (though there was reason to assume that it was.)