VOGONS


File Access Error!

Topic actions

First post, by ZeraX

User metadata
Rank Newbie
Rank
Newbie

Hello all i'm new here and new to DOSbox

I'm running into problem of executing an 16-bit .com file with DOSBox 0.74
the program is no-cd patch for Onimusha Warlords. For some reason the developer did it with a .com file.
which can't run in 64-bit windows 7.
when executing it in DOSbox it says
Patching OnimuPC.exe file
"File Access Error"

the OnimuPC.exe file is there in the same folder of the .com, and there no read-only attributes to it.

so i don't know what's causing the problem. thanks for any help given.

Reply 1 of 19, by Dominus

User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator

Does it have the right file access rights? If it's in a "program files" folder normal users don't have write access. (I know you wrote that it isn't read only but that may not cover for user rights)

Windows 3.1x guide for DOSBox
60 seconds guide to DOSBox
DOSBox SVN snapshot for macOS (10.4-11.x ppc/intel 32/64bit) notarized for gatekeeper

Reply 2 of 19, by ZeraX

User metadata
Rank Newbie
Rank
Newbie

I'm an Administrator on the PC, shouldn't it have problem with writing privileges ? i even tried running DOSbox with "run as administrator"

Reply 4 of 19, by ZeraX

User metadata
Rank Newbie
Rank
Newbie

UAC is disabled and the game is installed in D:\ partition

Reply 5 of 19, by collector

User metadata
Rank l33t
Rank
l33t

I'll assume that you have not overlooked something like the file is set to read only. Make sure that all file names and paths conform to the DOS 8.3 naming convention. Outside of this, the only other thing that I can think of is that it may be looking for a 2nd file that you missed placing in the folder.

The Sierra Help Pages -- New Sierra Game Installers -- Sierra Game Patches -- New Non-Sierra Game Installers

Reply 6 of 19, by ZeraX

User metadata
Rank Newbie
Rank
Newbie

It runs fine in 32-bit Win 7
so i did this before, no missing file i'm sure of this.

I did something new now, i launched Windows 98SE on VMware and took the files there, the cmd windows said "File Patched Successfully"
but i don't know it gives "don't send" window when i put them in the game installation folder. like the Win98 corrupted the file or the cmd wrote different code for Win98 or something.

everything was working fine in the 32-bit 7 😒

Reply 7 of 19, by ZeraX

User metadata
Rank Newbie
Rank
Newbie

If you people wish, i can attach both files here for you to try
maybe i'm not using DOSbox properly.

Reply 11 of 19, by ZeraX

User metadata
Rank Newbie
Rank
Newbie
Dominus wrote:

Hmm, yeah, you are right 😉
Maybe it does something you can only do on the Windows command prompt?

Nope, as i said it's 64-bit problem

9c47839177fd50f.jpg

Reply 12 of 19, by Dominus

User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator

The problem with Dosbox is not a 64bit problem.
That the program doesn't run in 64bit Windows doesn't negate what I wrote.

Windows 3.1x guide for DOSBox
60 seconds guide to DOSBox
DOSBox SVN snapshot for macOS (10.4-11.x ppc/intel 32/64bit) notarized for gatekeeper

Reply 13 of 19, by ripsaw8080

User metadata
Rank DOSBox Author
Rank
DOSBox Author

The patching program (ONIMU102.COM) is unable to open the executable file for patching because it uses LFN functions that are not implemented in DOSBox. Kind of strange that .COM format was chosen for a program released in 2007 that patches a Win32 executable... Anyway, maybe you can get it to work in DOSBox if you boot Win9X (not recommended) or DOS 7, but then you could use other VMs with about as much hassle.

Reply 15 of 19, by ZeraX

User metadata
Rank Newbie
Rank
Newbie

Did it in VMware and paste the patched .exe into the game.
the game runs now!
Though this method works, but it's require much more time. Wish DOSbox could make it more easier on me.

Anyway thanks everyone for your valuable time in this case.

Reply 16 of 19, by Dominus

User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator

I might be wrong, but can't you just keep the patched exe around forever and be done with having to patch it again and again?

Windows 3.1x guide for DOSBox
60 seconds guide to DOSBox
DOSBox SVN snapshot for macOS (10.4-11.x ppc/intel 32/64bit) notarized for gatekeeper

Reply 17 of 19, by ZeraX

User metadata
Rank Newbie
Rank
Newbie

Yeah that's what i just did, put it in a folder for future installation 😀

Reply 18 of 19, by ripsaw8080

User metadata
Rank DOSBox Author
Rank
DOSBox Author
collector wrote:

Or simply change the paths as I said earlier to "make sure that all file names and paths conform to the DOS 8.3 naming convention".

The files involved are already 8.3, but the filenames have nothing to do with the fact that the program is calling LFN functions that don't exist in DOS 5 or 6 (and therefore are not implemented in DOSBox).