Arduino IDE 2.2.1 won't start up, if Windows environment variable "TEMP" is assigned to a ram disk

PowerShell

IDE 1.8.19 was starting up fine with "Temp" assigned to a ram disk. (Primo Ramdisk)

1 Like

I believe you, IDE 1.8.* and 2.* are completely different (different programming language, different graphics, different frameworks) so they could have a different behaviour.

Anyway, I'm curious: I don't get why you need to point TEMP to a ram disk, nowadays we have fast hard disks, and very often SSDs, so why you can't switch to a "regular" TEMP directory? :wink:

I know docdoc, you can write books about the sense and nonsense of a ramdisk.
But that's my philosophy to protect the SSD from too many unnecessary write accesses in order to increase its lifespan.

I just wanted to inform others who are frustrated with the same problem.
And maybe it's a simple problem that can be solved quickly?

Googling a bit the error message I got this:

Quote:

Understanding the Error:
The “EISDIR: illegal operation on a directory, realpath” error occurs when using Vite on virtual and RAM disks that bypass the Volume Mounting Manager, such as ImDisk, due to a mismatch between the required disk management mechanism and the actual disk setup. Vite’s dependency on the fs.realpathSync.native method necessitates the involvement of the Mount Manager to locate mount points and perform related operations. However, since ImDisk does not interact with the Mount Manager, these operations result in errors.

The Solution: Implementing a Wrapper Function:
To overcome the “EISDIR” error and enable smooth building with Vite on virtual and RAM disks, a wrapper function can be created to handle the issue effectively. The wrapper function encapsulates the problematic code within a try-catch block, allowing for graceful error handling and resolution.

Thank you docdoc.
There is even a solution described there.
What do you think, should we report this issue at github? (I've never done that)

Hi @m8nix. Thanks for your report. The Arduino IDE developers are tracking this bug here:

If you have a GitHub account, you can subscribe to that issue to get notifications of any new developments related to this subject:

image

I have the same issue as @m8nix, in which I use ImDisk to turn 64GB ram to d: and set d:\TEMP as temp dir.
Looking at the bug tracking @ptillisch posted, there is a workaround for 2.1.1, but the file structure is different on 2.2.1, where the specific .js file is not there anymore.
Does anyone know where
fs.realpath.native and fs.realpathSync.native
keys are now located?

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.