I'm thinking that this is more of a Windows problem than VDMSound.

Can you try creating a folder with your friends username and try copying files to and from this folder? Also create a subfolder called TEMP in this folder and do the same.

Nah, it isn't a windows problem, windows doesn't have any problem accessing hebrew folder names if the hebrew language is installed, for example, my computer's XP is in english but has hebrew installed and I'm always working with hebrew folders and files, not to metion that he has a full hebrew windows (I.E. a hebrew MUI - if you know what that is).
and creating a Temp folder where you specified dosn't change anything (why should it?).

I'm pretty sure this is a VDMSound problem, and I have also attached the error message below. It's just your regular "16 bit MS-DOS Subsystem" error though.

Try copying both AUTOEXEC.NT and CONFIG.NT from \Windows\Repair folder to \Windows\System32

You are Joking, right? 😕

No, I AM NOT.

I see, I thought you were just making a joke about the expression I used:

Og wrote:

It's just your regular "16 bit MS-DOS Subsystem" error

Sorry.

At any rate, I am very aware of the infamous autoexec.nt error, however as you can clearly see in the picture I have attached in my last post there is no reference to the aforementioned infamous file. The autoexec.nt error looks like this:

Could you translate to English, please? I cannot understand Hebrew.

I think that DosFreak is right. Remember that VDMS is using the NTVDM and sees paths and file names as DOS does, not Windows. If you don't want to reset the temp path, you could just use DOSBox.

eL_PuSHeR: Sure 😀 (I'm assuming you mean the 1st error):
----
Title: 16 bit MS-DOS Subsystem
[1st line is the location of the temp folder with visible hebrew characters]
[2nd line starts with the location of the temp folder but with hebrew characters converted to question marks, followed by this text:]The system file is not suitable for running MS-DOS or Microsoft Windows applications. Choose 'Close' to terminate the application.
----
In other words, the text is identical to the autoexec.nt error, however, the files are generated(and generated correctly) in the temp folder. VDMS simply can't read them from there.

collector: Thank you for your help, but I am using DOSBox all the time, it is an amazing emulator, however, sometimes I just want to use NTVDM for many reasons which I will not specify here.
Oh, and NTVDM shouldn't have a problem with hebrew either:

I have an idea that might work for you.

Right-click on My PC > Properties > Advanced Options > Environment Variables > System Variables > Make sure there is both a TEMP and TMP variables. Modify them accordingly.

Check image below. It's in Spanish, but I think you will get the picture. The idea is to make the TEMP paths variables using shortnames.

Make a System Restore point before, just to be on the safe side.

Also, you might need to uninstall/reinstall VDMSound again after making those changes.

The reason I mentioned creating a folder with the characters is I've had alot of situations with folders in Windows where if they were really long and used "unusual" characters that I would have issues copying to and from the folder. (Nothing to do with NTVDM, just usual Windows folder oddness).

<Sigh>

I give up... Thanks to everyone who tried to help.

By the way, if Vlad R. happens to come by this thread and has something to say about this, I'll be happy to hear(read) it.

Regards,
Og.

heh. There's about a 99.1% chance that he won't. 😉

Hey, Og. Did you try setting temp folder to a short name using non-Hebrew characters?

In his first post he said that it worked when he did this

Furthermore, after changing the temporary files environment variable to a different(existing) folder, VDMS ran fine.

but for some reason this is not an acceptable solution. Personally, I like to set my temp folder to C:\TEMP anyway, so that I can easily get to it. There is a lot that doesn't get deleted after it is not being used anymore.

Og - did you take a look at those "unsuiteable" temp-files? There is a small time window between the time when VDMSound generates the files, and when it removes them again. Run a script in another window that constantly tries to copy the temp-files into a safe location. Then you can look at what they contain, and maybe spot what makes them "unsuitable".

Yepp, it's a Windows problem alright. LaunchPad generates a temporary .pif (that's Windows) file that refers to a temporary CONFIG.NT and AUTOEXEC.NT files, but Widnows gives the error you see when the paths to AUTOEXEC.NT/CONFIG.NT contain funny stuff.

NOW, the latest VDMSound from Vogons puts the short names inside the .pif file to go around this kind of problem (and other problems, such as long paths "C:\Documents and Settings\Very Long User Name" blowing the 64-char limit inside the .pif format) but Windows still screws up IIRC hence your error.

Temporary .pif files are kept about 5 seconds IIRC in %TEMP% so you can make a copy quickly before it's erased by VDMSound to check if it has the correct (short) paths inside and confirm whether Windows screws up despite that, if not then check 1) that you have a good VDMSound and 2) that short file names are active on your disk ("DIR /X" in a command prompt to see if dirs have both the long and short file names)

V.