Thursday, October 08, 2020

Megarec.exe for Flashing Dell H310 from HP

Yes, the formatting for this post is ugly to say the least. Maybe I'll fix it since I'm out of work...if you look on the right and 'Buy me a Cup of Coffee'.

Here's where you get the needed files. I made this post because I don't like using strange programs from who knows where:

This assumes your computer can boot via BIOS from a DOS usb stick and you've prepared it. My Poweredge T310 can, no problem.
Copy of sbrempty.bin (to zero part of the controller's ROM):

Paranoid about the contents of sbrempty.bin?
Yeah, me too:

Portions of these instructions cribbed from somewhere...there are about 1000 reposts.

Copy the files you'll need to the root USB folder. (C:\). You'll need megarec.exe, sbrempty.bin, 6GBPSAS.fw, sas2flsh.exe, and optionally if you want a BIOS a copy of mptsas2.rom

  • megarec.exe -writesbr 0 sbrempty.bin
    • If this command fails it should be safe to proceed to step 2. (Note from me: Worked fine for me.)
  • megarec.exe -cleanflash 0
  • Reboot the computer and boot back into the USB drive.
  • sas2flsh.exe -o -f 6GBPSAS.fwAlso, if you just type 'sas2flsh -listall' IIRC mine just said the board was operational and let me input 6GBPSAS.FW as the firmware to flash when it asked. Reboot.
If you want to add the BIOS (which you don't need for UNRAID but I think it might be nice to have, will respond back if anything significant is useful in the BIOS) you can do that in a separate step:

sas2flsh.exe -b mptsas2.rom Reboot.

When you reboot, if you want to enter the controller BIOS (mine complained about being disabled) keep hitting Ctrl-C.

Works fine so far! rsyncing my Windows GUI VM data on a DAS Drobo over to my Unraid server via an NFS mount...don't do rsync over SMB if you value your life.

Oxed for Mac OS X hex file viewing:

Wednesday, October 07, 2020

OpenOffice crashed when Opening Passworded File. I'm on Version 4.1.7 and OS X 10.14.6

I'm out of work. :( If this fixes your problem, by me a cup of coffee using the link on the right side of this blog. If I had $1....I'd have a dollar. 

Crash dump:

Path:                  /Applications/

Identifier:            org.openoffice.script

Version:               4.1.7 (???)

Code Type:             X86-64 (Native)

Parent Process:        ??? [1]

Responsible:           soffice [9009]

User ID:               501

Date/Time:             2020-10-07 11:32:28.271 -0500

OS Version:            Mac OS X 10.14.6 (18G6032)

Report Version:        12

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue:

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)

Exception Codes:       KERN_INVALID_ADDRESS at 0x0000724565a10950

Exception Note:        EXC_CORPSE_NOTIFY


Ugly, Right?

I found this fix and knock on wood, it worked just now after consistently crashing over and over. I could start a new doc but when I opened a passworded file I've used over and over for years...crash.

Mac OS, it just works, right? B.S. it does. TBF, it's because this is probably because in my case it's an upgrade over an upgrade over an upgrade....

From This thread:

"Also, check in your user preferences to see if Java is enabled.

On menubar: OpenOffice/Preferences/OpenOffice/Java
Make sure "Use a Java Runtime Environment" is checked and there is a check mark beside a installed JRE."

In my case, there was no runtime selected. I also did the bit about allowing OpenOffice to control my machine found in the System Preferences pane at Security and Privacy -=> Accessibility. I added OpenOffice to the list.

Google Find us on Google+ Website: