How to open a .dwg drawing created on a 32bit version of AutoCad drawing in Windows 10

[GreensandsParticipant @greensands]

Probally off topic but help is required – I have just updated my printer to an HP 2700e running on Windows 10 but this has created the problem of how to print my AutoCad .dwg drawings created on a 32bit Windows XP machine. Any suggests most welcomed.

[GreensandsParticipant @greensands]

[Martin ConnellyParticipant @martinconnelly55370]

Download the latest, free, DWG viewer TrueView 2021 from Autodesk. It works in W10 and prints either from the models or layouts.

Martin C

Edited By Martin Connelly on 07/04/2022 23:44:15

[Paul LousickParticipant @paullousick59116]

I'm a bit confused with the question (does not take much to do that now days)

Updating the printer should not be a problem if you have the correct driver and should work with any computer. If your computer has been upgraded to Win 10, you should still be able to run your old Autocad. It should not matter if the .dwg drawings were created on a 32 bit or 64 bit machine. Newer versions of Autocad should be able to open older versions but the reverse is not always possible.

Paul

[Martin ConnellyParticipant @martinconnelly55370]

It's a problem in AutoCad not sending data to the W10 printer correctly. Even trying to print to a pdf printer fails. I can use AutoCad on my W10 machine but cannot print from it. I just use TrueView as the simplest way of printing from the saved drawings. There may be a better work around but I have a simple solution so I use it.

Martin C

[Andy CarlsonParticipant @andycarlson18141]

The ODA file converter is free and may help if it's an issue with the file itself.

[Robin KingParticipant @robinking15611]

I have exactly the same problem – in my case drawings created in AutoCAD LT on my old Windows Vista based pc. Using Trueview on my other Win 10 pc allows me to print off those old files easily.

[HowiParticipant @howi]

Posted by Paul Lousick on 08/04/2022 00:00:24:

I'm a bit confused with the question (does not take much to do that now days)

Updating the printer should not be a problem if you have the correct driver and should work with any computer. If your computer has been upgraded to Win 10, you should still be able to run your old Autocad. It should not matter if the .dwg drawings were created on a 32 bit or 64 bit machine. Newer versions of Autocad should be able to open older versions but the reverse is not always possible.

Paul

Me too, it should not matter what computer or what printer.

I suspect the printer has not been set up properly and rather than sort out the problem, some have chosen to go for a work around.

[Paul LousickParticipant @paullousick59116]

I cannot imagine a big company like Autodesk selling a product that cannot print older drawings on a new computer and operating system.

People would not buy Autocad.????

[Martin ConnellyParticipant @martinconnelly55370]

I am still using AutoCad 2010, that is where the problem lies. It is still fully functional as far as creating a model and drawing are concerned but does not communicate well with W10 printing. Since I am no longer working as an engineer I see no point in updating something that works and does what I want.

Martin C

[Paul LousickParticipant @paullousick59116]

A quick internet search found this post: **LINK**

These issues are related to HP Drivers not being compatible for Windows 10. Here’s a list of Windows 10 Compatible Printers and Drivers: HP Printers – Windows 10 Compatible Printers
In most cases, you can fix this issue by downloading and installing the HP Universal Driver: HP Universal Print Driver Series for Windows
For other possible solutions to these issues, please visit the following AKN:
HP printers do not work with AutoCAD on Windows 8 or newer systems
Looking for more assistance? We can help! Whether you need help troubleshooting technical issues, or you’re interested in exploring our training or service offerings, contact us to get started.

[SillyOldDufferModerator @sillyoldduffer]

This sort of problem is difficult to diagnose. Like as not it's caused by something internal coming adrift after a long accumulation of changes:

• Windows 10 is not identical to Windows 8,7, Vista, XP, 2000, NT, W-11, or MSDOS
• 64 bit is not 100% compatible with 32 bit, and – over time – less effort is put into it.
• AutoCAD was upgraded 24 times between 1982 and 2010, and file formats like DWG followed suit
• PDF, HPGL, Postscript and other printer languages have all been repeatedly updated
• Printer technology and the necessary drivers have been changed repeatedly too.

Nothing lasts for ever, which is why software vendors recommend keeping computer systems up to date. Almost the worst thing a computer user can do is stick loyally to products well past their best-before date and then be forced into a gigantic jump when something claps out. Likely to find software doesn't work, went out of business, or doesn't understand it's own obsolete file formats. Or is incompatible with everything else on the system.

It's analogous to the way English changed over time gradually making it hard for later generations to decode. This is Chaucer:

men myght axe me why soo
I may not sleepe, and what me is.
But natheles, who aske this
Leseth his asking trewely.
Myselven can not telle why
The sothe…

At the moment the scale of the problem is unbounded. Anything from a simple tweak to catastrophically complicated.

I fear it's not a simple tweak because PDF and the Physical Printer are both refuseniks. It suggests the failure is inside AutoCAD rather than the printer or W10. The code that translates AutoCADs internal format into printable forms is in trouble. As sending random stream of bytes causes havoc, receiving software generally puts considerable effort into rejecting anything it doesn't understand. If W10 only understands PDF version 2.0 or later, it will bounce an earlier format submitted by an ancient program. Same with the print language. Coukld be the issue here.

Fortunately, vendors sometimes provide software to help customers migrate from past to future. TrueView looks good. Large organisations often get into a pickle over this: engineers warning about the risk of creeping obsolescence are often ignored by managers focussed on today money. If the poo hits the fan, it's possible to contract software vendors to sort out the mess by bespoking conversion software. Two problems: conversions are often flawed, requiring manual fixes, and expensive to buy, even by big rich company standards.

Don't give up too quickly – might be an easy fix. If all else fails, the Windows log files probably show where the failure occurs. Unfortunately, understanding logs is a specialist skill. You might start here, noting the firm profits by selling software help decode logs.

Dave

[Author]

Posts