Steps to reproduce:

0. Windows 7 x64 SP1 Ultimate with Fopnu 1.68 portable.

1. Create ImDisk RAMDISK Volume using https://sourceforge.net/projects/imdisk-toolkit/files/

2. Download Fopnu portable from https://www.fopnu.com/download/portable.html

3. Run fopnu_Windows64bit.exe

4. It will crash.

Fopnu works fine on "normal" non ImDisk RAMDISK volumes, such as C: but I don't want to run it from there.

Also note that Tixati works perfectly with ImDisk RAMDISK volumes.
But Fopnu doesn't seem to work with ImDisk RAMDISK volumes.

First time user of Fopnu here. Just wanted to test out the software. But it crashed on startup.
Please fix Kevin and other maintainers.

Thanks!

Thanks for reporting this. If you are getting crash reports please send them, or post them here.

If you run the 32bit portable version does it crash? I'm not familiar with ImDisk RAMDISK, what exactly is that, I'm guessing a harddrive? If you run Fopnu on the ImDisk with the regular exe and with the fopnu_local_instance_check.txt file, does it still crash?

> Thanks for reporting this. If you are getting crash reports please send them, or post them here.

A fopnu_crash_report .dat file was generated. But it is a binary file.

I would like to read and confirm what data I'll be sending first before I send it.

I tried to view it using https://www.nirsoft.net/utils/blue_screen_view.html

But it doesn't work.

How do I view the data in fopnu_crash_report.dat file on Windows 7?

Thanks!

>  If you run the 32bit portable version does it crash?

When I run fopnu_Windows32bit.exe from an ImDisk RAMDISK volume, nothing happens.

The process just stays in task manager without any window showing up.

   $ tasklist | grep fopnu_Windows32bit.exe
   fopnu_Windows32bit.exe       19380 Console                    5     15,376 K


> I'm not familiar with ImDisk RAMDISK, what exactly is that, I'm guessing a harddrive?

It's a RAMDISK.

Basically, it creates a new volume on My Computer/This-PC by allocating a user specified portion of your free RAM.

It's typically used to minimize disk wear.

> If you run Fopnu on the ImDisk with the regular exe and with the fopnu_local_instance_check.txt file, does it still crash?

What does fopnu_local_instance_check.txt do ?

Also I don't want to run the regular non-portable "installer" version of Fopnu.

Also I've already stated in my OP that Fopnu(portable) works fine on "normal" non ImDisk RAMDISK volumes, such as when running from C: but I don't want to run it from there.

The fopnu_local_instance_check.txt file is like using the standalone but as a second instance. If you put the fopnu exe and the fopnu_local_instance_check.txt file in a folder and run the exe all the dat files will be in that folder. It does not install Fopnu, just runs it from the folder. Like portable or standalone. The fopnu_local_instance_check.txt file just allows you to run more than 1 copy at a time.

I understand being nervous about sending in a crash report but the dev wont do anything with the crash report you send, except fix your problem. I'm pretty sure those reports really only have where in memory you crashed. Others have posted them here in the forum before. It's the easiest way for the dev to fix things.

> The fopnu_local_instance_check.txt file is like using the standalone but as a second instance. If you put the fopnu exe and the fopnu_local_instance_check.txt file in a folder and run the exe all the dat files will be in that folder. It does not install Fopnu, just runs it from the folder. Like portable or standalone. The fopnu_local_instance_check.txt file just allows you to run more than 1 copy at a time.

I created fopnu_local_instance_check.txt but the portable version of fopnu still crashed.

Turns out I also had to delete fopnu_portable_mode.txt

And that seems to have done the trick.

Fopnu is able to start now from an ImDisk RAMDisk volume.

Thanks for the help!

> I understand being nervous about sending in a crash report but the dev wont do anything with the crash report you send, except fix your problem. I'm pretty sure those reports really only have where in memory you crashed. Others have posted them here in the forum before. It's the easiest way for the dev to fix things.

Fopnu is closed-source software whose bug report generation method is also closed source.

A user merely wanting to see what's in a bug report surely isn't that big of an ask.

I'm sure Kevin and others have good intentions, and I really do want to send the crash report, but I just want to see what's in the crash report before I send it.

So please do let me know how to open/view the fopnu_crash_report .dat file.

Thanks.

What is this Tixati .dat file? While Windows uses .dmp files for system-wide crashes, Tixati generates their own crash dumps. Tixati uses the .dat extension for these files.

That .dat file is a minidump specifically for the Tixati program. A minidump is a small file created by Tixati during a crash. Instead of saving everything that was running in your RAM (which could be 16GB or more), a minidump only grabs the bare essentials needed for basic debugging. When Tixati crashed, it took a quick snapshot of its own memory space so the developers can see exactly which line of code caused the failure.

What does it contain? Because it is an application-specific minidump, it contains data highly technical to Tixati's internal operations like:

The Crash Signature: The exact error code or exception that caused Tixati to force-close.
The Call Stack: The sequence of internal functions Tixati was executing right before it crashed.
Memory Register States: Tiny bits of data the CPU was processing for Tixati at that exact millisecond.

I haven't tried this myself, but you could try using a free Microsoft tool called WinDbg (Windows Debugger), which you can download from the Microsoft Store, to see what's inside before sending it. No idea if this will work for sure.

Crash dumps are the single most effective way for developers to fix bugs. Tixati's developers are highly reputable, and they use these logs strictly for debugging.

No, WinDBG doesn't work. It needs debugging symbols for Fopnu.

Anyway here's the crash report from my Windows 7 32 bit Virtual Machine.
The 32 bit portable version of Fopnu crashed when I tried to run from ImDisk RAMDISK, but the regular installer version - fopnu-1.68-1.win32-install - works perfectly.

Hope to see this issue fixed.

Thanks.

fopnu_crash_report.dat.asc below.

I've encrypted the report using https://www.tixati.com/tixati.key

-----BEGIN PGP MESSAGE-----
(Log removed by Mod and sent to Dev)
-----END PGP MESSAGE-----