3ds2bin Path/File Access Error. - by Derspegn
Derspegn on 14/6/2015 at 03:10
(Original) 3ds2bin requires n3ds2e.exe, BSP.exe, MeshBld.exe, and View.exe (optional). The program has located the four .exe files, but I am getting "Run-Time Error '75': Path/File access error" after I press "Go!"
(+Edit) I've also located others - biped.map, 3dstoE, Eto3ds, and I still get the same error.
Any suggestions for this? I don't know how to code, so other than Blender, this is probably the only other program I am likely to use to convert files.
Inline Image:
https://imageshack.com/i/f0fRB87Lj
LarryG on 14/6/2015 at 03:15
(
https://msdn.microsoft.com/en-us/library/aa264531%28v=vs.60%29.aspx)
Somewhere in your setup for 3ds2bin, a reference is made to a file that no longer exists, has been renamed, or you don't have access to. You will have to identify then correct the filename or permit yourself to it.
Bottom line: you probably didn't type the path and file name correctly for one of the files needed. You also may need administrator access (who knows why) and aren't running under an administrator id.
Derspegn on 14/6/2015 at 03:47
Quote Posted by LarryG
(
https://msdn.microsoft.com/en-us/library/aa264531%28v=vs.60%29.aspx)
Somewhere in your setup for 3ds2bin, a reference is made to a file that no longer exists, has been renamed, or you don't have access to. You will have to identify then correct the filename or permit yourself to it.
Bottom line: you probably didn't type the path and file name correctly for one of the files needed. You also may need administrator access (who knows why) and aren't running under an administrator id.
When 3ds2bin.exe prompted me for the other files, I located them with matching titles in my Thief 2 directory. I run 3ds2bin.exe as an administrator
R Soul on 14/6/2015 at 18:12
It's strange that it doesn't work even when you run it in admin mode. The program generates one or more temporary files during conversion (for example, an .e file), as well as the converted file at the end. If any of these are created anywhere inside Program Files (x86 or otherwise) Windows might try to protect you by saying no, despite the admin status.
Try moving the program and all the other .exe files out of Program Files so they can work with an ordinary folder. You can edit the .ini file to change ThiefPath so the object is also created outside of PF. If that works, you can move your T2 folder somewhere else too.
Derspegn on 15/6/2015 at 00:46
Quote Posted by R Soul
It's strange that it doesn't work even when you run it in admin mode. The program generates one or more temporary files during conversion (for example, an .e file), as well as the converted file at the end. If any of these are created anywhere inside Program Files (x86 or otherwise) Windows might try to protect you by saying no, despite the admin status.
Try moving the program and all the other .exe files out of Program Files so they can work with an ordinary folder. You can edit the .ini file to change ThiefPath so the object is also created outside of PF. If that works, you can move your T2 folder somewhere else too.
I can try these methods to see what happens. I never put my T2 installs into Program Files because of protection issues. I have separate installs directly in my external hard drive (I:/gamesb/thiefeditor), and then a non-Dromed install is under "I:/gamesf/thiefmetalage". I copied 3ds2bin and the other associated files from "I:/Libraries/games/EIDOS DROMED," so I'm not sure if "Libraries" is equally as protective as Program Files, but I've never had any issues with "Libraries" in the past.
Derspegn on 15/6/2015 at 12:12
Here are a couple of options:
1. Make a level without converting any .3DS files and wait for alpha/beta testers to tweak items (level will involve the switch & return of two babies between cribs -- "Dewdrop" doll is the closest, but doesn't look like a baby.
2. Instead of using an external hard drive, put an install on the regular hard drive and see if 3DS2bin performs differently (due to potential cable transfer issues).
LarryG on 15/6/2015 at 14:16
There is no difference between internal and external HDs as far as 3ds2bin is concerned. I have everything on an external HD and it works fine. You just have the setup for 3ds2bin messed up somehow & you should never have Thief installed in your C:/Program Files directory. Windows treats that specially. Put them anywhere but there. Then reinstall 3ds2bin and all the helper files. Make sure that you don't have any typos.
Derspegn on 16/6/2015 at 02:50
When I converted a small part of a .3ds object I did get a .bin, but only noticed that after I downloaded a different 3ds2bin version. As per the suggestions regarding placement into the custom objects folder from the Low Poly Guild, I have put all related files into my "Obj" folder, which is where I discovered the bin. When I tried putting both this .bin and a .bin I converted months ago into the object hierarchy, I get the corner pyramid like you see in the attached photos. I see this for both of them, even though one is under physical --> TerrainLike --> climable --> Rope, and the other is under Missing. I would like to know what else is required besides simply placing it in order for it to be viewable. I have been trying to search this topic but haven't found much.
Inline Image:
https://imageshack.com/i/pdeW5ZkApInline Image:
https://imageshack.com/i/f0WIUEZWp
LarryG on 16/6/2015 at 02:58
The wedge indicates that the object name you typed doesn't correspond to any legitimate bin file in your OBJ directory.
So.
There is no way to tell from what you have described just what is going wrong. Are the bins you created good or are they bad? Are they in the correct directory or not? Did you create the hierarchy element that refers to them correctly or not? Is the reference to them on the concrete object good?
1) You mention objects from the defunct low poly guild. Where did you put the bins and where did you put the associated textures? If you refer to one of those objects in a concrete, do you get the wedge or the anticipated object?
2) Are you still getting the Path/File Access Error that is the name of this thread, or have you fixed that?
3. What do you mean you converted part of a 3ds object? The tools don't let you do that. You either succeeded in converting the whole object or the conversion failed. That's how it happens.
Derspegn on 16/6/2015 at 03:25
Quote Posted by LarryG
The wedge indicates that the object name you typed doesn't correspond to any legitimate bin file in your OBJ directory.
So.
There is no way to tell from what you have described just what is going wrong. Are the bins you created good or are they bad? Are they in the correct directory or not? Did you create the hierarchy element that refers to them correctly or not? Is the reference to them on the concrete object good?
1) You mention objects from the defunct low poly guild. Where did you put the bins and where did you put the associated textures? If you refer to one of those objects in a concrete, do you get the wedge or the anticipated object?
2) Are you still getting the Path/File Access Error that is the name of this thread, or have you fixed that?
3. What do you mean you converted part of a 3ds object? The tools don't let you do that. You either succeeded in converting the whole object or the conversion failed. That's how it happens.
Inline Image:
https://imageshack.com/i/eykppydOjInline Image:
https://imageshack.com/i/exd3qYI2j1) I placed the bins into my obj folder - I reverted to Dromed for v1.21, so I currently do not have the obj/txt16 folders as they were with v1.22. As for textures, the bins did not originally have any textures.
2) The Path/File Access Error still appears, although it is strange how a .bin appeared
3) Using Blender, I took an object that had separable parts, deleted a majority to reduce size, and converted a part of it. Months ago, When I got bins from an object, it was because I split seams on the grid over the object, and broke it up into smaller pieces, and as a result the .bins were converted. Sorry for being a noob, I'm just trying to better understand Dromed.