Fbx 2013.3 Converter For Windows 64-bit
Tordis Hurrle
I realize that there will likely be no special converter programs or anything easy like that for such a task, but it imperative that I find some way to get a 16-bit program to run in 64-bit Windows. Due to the large amount of resources that must be dedicated to them, emulators will not be a good solution.
The idea I had for this project was to decompile all the code from a 16-bit program, copy it, and re-compile it into 64-bit code. Is this at all possible using Eclipse or another programming environment?
The problem goes beyond translating 16-bit instructions with 64-bit instructions. There is also the ABI (Application Binary Interface) used by the program to communicate with the rest of the system. A 16-bit program likely uses a lot of DOS calls and it's not unlikely it tries to access hardware directly too. There is no way this can be translated automatically. Even if such a solution existed, I highly doubt the result would be more efficient than running in a virtual machine (which actually is very efficient). Further more, programs written for 16-bit environment are often not very scalable, and completely unable to handle amounts of data beyond the capacities of the original target platform.
I'm in a real mess now. I have a 32bit driver for my Frontech 2215 e-cam . I have searched the internet was unable to find a 64bit driver even in the manufacturer's site. Hope someone could come up with a solution.
Not possible, for so many reasons. At the very least it requires a re-compile, for which you'll need the driver source code (which I'm guessing Frontech has not made public). And it'll likely require a lot of other changes as well. Driver ports are rarely trivial.
Most people say it's not possible however, it may be possible but, it is probably not going to be easy, may not be legal, could slow down your computer and may even cause programs or the computer itself to crash. If you still want to try then here are some arduous avenues that you could take to accomplish your goal.
Possibility 1 - Recompile the driver
In theory, if you can dissemble the driver to see how it works and then re-write the driver to be functional in a 64-bit environment. However, this solution may not be legal or easy to do. This would also be harder the more complex the driver is.
Possibility 2 - Emulation
I am no expert on the internal workings of 32-bit and 64-bit drivers however, If you can emulate an entire 32-bit computer on a 64-bit computer then it should be possible.
In theory, you would need to either find or build a wrapper for the 32-bit driver. This driver would be a 64-bit driver and would act as a miniature emulator for the 32-bit driver to exist in.
However, the bigger question in this case is how fast does the driver needs to operate. The reason why this is important is because if you did manage to convert the data, it may take longer for the driver to operate and if a driver requires a certain amount of speed to operate, it could cause programs and possibly your computer to crash if your computer isn't designed to deal with slow drivers.
The plus side to this method is that you would be able to avoid legal issues that may come from decompiling the driver.
Installing Unsigned Drivers:
In order to install your driver unsigned, you will have to enter into a special mode to Disable driver signature enforcement or through a different method. Here is a link to a tutorial on how to do that:
-to-install-unsigned-drivers-in-windows-10/
End Note
At the end of the day, it all comes down to how much time are you willing to spend to make a driver to function and if it is worth the risk. And so far, I have been unable to find any such drivers online.
So, yes, sometimes you can, and it probably all depends what those .SYS files get up to and how they were written. Exactly what you need to do to convert the old .INF file to the new is complex - fortunately he provided one in this case. If one diffs the files they are not similar at all.
I recently installed ACADLT 2000 on my Win 10 PC thanks to your help! Everything is working great, including selecting one of my printers, except that when I try to print, ACADLT says it plots, but refuses to print anything and just stares at me (and laughs). Your help is appreciated.
These old programs were never designed to run on future OS systems, besides since August 31 2019 any version of Autocad 2010 or older will no longer be activated, so it's not worth the effort if you have older versions running on a computer don't expect to be able to move it to a newer computer.
Autodesk killed off reauthorizing of 2010 and older software as of August 31 2019, read all about it here -explore/caas/simplecontent/content/previous-ver...
Sorry, you missed the deadline. There is nothing you can do about it today.
If you find Autodesk software subscriptions too expensive, there are many other CAD packages out there with no subscription options (initial cost may still be comparably high) that you can go get and use.
Hi leebewright, not sure what is happenning on yours. There is no online activation I know of in AutoCAD LT 2000 so that is unlikely a factor in this situation (can't remember exactly, but I think online activations started around 2004 or so).
When you say nothing happens, do you mean you double-click the "AutoCAD LT 2000" shortcut after completing installation and nothing opens? If that is the case, I have not run into this. I would try right-clicking the shortcut, then "Compatibility" tab, and check the box, "Run this program in compatibility mode for:" and try different versions of windows.
Interestingly, mine works fine with or without compatibility mode, except printing. When I want to print I need to put it in capability mode or I get an error when opening a paper space tab. (I normally operate NOT in compatibility mode because I use AutoHotkey for some helper macros while drawing, and autohotkey does not seem to function when AutoCAD is run in compatibility mode. Probably more information than needed, but that is why I use both modes.)
pendean, thanks for the info. Unfortunately I did not save the update. I did take a quick look in my archive files because that is the type of thing I save forever until I discard software. But, not too big a deal for me right now, as I do not print too often at this point.
Thanks for sharing, but for me, those steps didn't work out so well I'm probably doing something wrong, but for me the main issue being the Properties palette not working, that's pretty much a deal breaker for me. Also, your steps for the DDE issue are ok, but I get a new instance of AutoCAD each time I open from Explorer (instead of the DWG being hosted in one instance of AutoCAD (multiple Windows) which is annoying. Also, I just noticed some of the commands I use are not working, for instance, IMAGE gives "unknown command"... Ouch - MTEXT completely bombs out.... Hmm - I have a feeling that those issues you mention in setup might have something to do with it? Do you see the same problems? Any ideas?
IMAGES: The image command does bring up a dialog for me, but I cannot browse to add an image. My work-around is to Edit->Copy from an image viewer, then in AutoCAD Edit->Paste Special->Bitmap. It isn't perfect because you now have to interact with the image with right-click and drag-drop. It is irritating, but workable sort of.
Note that I am currently running without the ACAD.bat work-around. I was able to associate with the right-click->Open With" to aclt.exe. On my system it opens multiple files in one instance (at least with the current windows updates..)
appreciate your reply. I believe I was running into Windows 10 security issues (LT 2000 is understandably ignorant about running 20 years in the future on Windows 10). I believe LT setup was failing due to permissions, cost me a lot of time messing around
In the end, I solved it simply by using the Longbow solution and followed their instructions for installing LT 2000 on Windows 10 64bit - points to note: I had no setup issues at all, Properties is working perfectly, MText also not crashing. All commands are running as far as I can see. I note plotting worked straight out the box using Longbow. Cost some $ but recommended as they were very responsive to my questions and got me running very quickly on my brand new Surface Pro Windows 10
i have the same issue as another user. when i use the setup install file with all the settings as per the recommendations nothing happens. i get a blue circle for a few seconds that then goes and nothing is shown. i cannot then open the installer again. when i go to take manager the install sheild is shown in background processes but thats all. i have played with all the compatibility options when tried changing the resolution of my screen nothing seems to bring up the installation program.
I recently followed your steps, and had no issues installing and running ACAD2000 on a windows 10, 64 bit system. Thank you so much! I had been saving up for the Longbow converter, and was disappointed to see that they had raised the price. A search brought me to your post, and I am so glad it did.
e59dfda104