jloach

Hi Chris Tried IC5 with Hotfix 2. Nogoodsky. I never tried installing IronCad AFTER MD4. Also, never checked BOMs. I applied the fix to move the og70as.dll file from system32 to MDT, but in this case it didn't help. I'll borrow an AutoCad 2000i at the end of this week and give it a whirl. I suspect that the problem may lie in the Mechanical Desktop crap. Evaluating that program a couple of years ago was a very futile and frustrating experience!! All the filesystems I'm using are NTFS, on SCSI. I'll let everyone know how we do with AutoCad 2000i instead of MDT4. I think it will work. Thank you!

AutoDesk has 4 service packs for MD4. When I get a chance I'll apply them and go through the exercise again. I'd love to know, though, if anyone else is having any luck running AutoCad with IronCad. Thank you!

Windows XP Pro, with all the latest microsoft critical updates. MD4, with SP1. I'll check for later SPs. MD4 was extremely buggy when it came out (apart from being nearly impossible to be creative and productive with). Just for fun, I made sure that Ironcad directories were ahead of MD4's in the path variable. Didn't help. IronCadded the last hour and a half fine, with MD4 removed. It does appear to be the problem. Thank you! John

Thanks Chris, but copying those files didn't help. I'll remove AutoCad, re-install IronCad, and procrastinate on purchasing an AutoCad 2002 license for a little while. Gotta get some IronCad work done! Cheers, John

I reformatted and reinstalled XP, and started with a minimal system containing only Office 2000 and Ironcad 5. Beautiful. Installed McAfee VirusScan 6 and still ran great. Then installed AutoCad Mechanical Desktop 4 in order to run AutoCad for customer compatibility. IronCad started freezing. I uninstalled AutoCad and IronCad, and reinstalled IronCad. IronCad now runs fine again. So the problem seems to be an incompatibility between MD4 (or AutoCad 2000) and IronCad. (BTW, I'm also quite incompatible with AutoCad!). IronCad and MD4 ran fine together in Windows 2K. Problems only appeared in XP. Unfortunately I do need AutoCad, so I'll probably pick up AutoCad LT 2002, so as to minimize the investment. Hopefully whatever was causing the problem has been cleared up in the later AutoCad release. Is anyone is successfully running IronCad and AutoCad LT together in XP? Thank you all for listening to this saga. John

Bummer. Just froze again. Not sure what to try next, but experimenting with this stuff sure cuts into your drafting time. And forgetting to save regularly can make for quite a bit of repeated work! The dual athlon on XP with FireGL2 runs really great, though.

Still had a lockup after the mouse driver update. AMD has an AGP driver update which I installed. So far so good. miniport_522_win2k.exe (AMD AGP Driver Version 5.22 for Windows 2000)

Hi all Running fine today, with the only change being I installed the latest Microsoft Intellimouse driver from www.microsoft.com over the one that came with XP. Hopefully that's it. John

Thanks for the tips, Chris. This is a recent install, with a newly formatted disk and a full version of XP Pro. I'd sure hate to have to start over. Painful. I'll try running for a while without some of the extraneous background utilities like McAfee and DirectCD. Between stops, IronCad is fabulous!!!! Cheers, John

Hi! Does anyone have a blue-screen problem with XP running IC5? Two or three times a day, while rotating a few items with the tri-ball, the screen will suddenly freeze. No mouse movements or keyboard presses respond. After about 15 seconds, the system blue-screens, reporting a critical error 5, which it blames on some device in the system having a bad driver or something. No specific suggestions, except to perhaps disable caching and shadowing in CMOS. After a reboot, everything's fine again. I thought is may have been the soundcard, but it happens with that removed as well. I bet it's the video driver, but the latest has been installed. IC5 Hotfix 2 Windows XP Pro Asus A7M266-D Dual Athlon MP 1900+ Fire GL2 Soundblaster Live 5.1 Adaptec SCSI 19160 Thanks all. John

Great news! This was a problem caused by having AutoCad installed. Fixed by moving a file, as indicated in the 'AutoCad apps can break IronCad 5.0 install' posting. Thanks, Chris!!! John

I removed and reinstalled with no luck. I'll remove, take IronCad out of the registry, and download the install file again. I only use parameters for creating slots - you just fill in the length and diameter into the parameter table and the slot gets built. Saves a bunch of time. I use Bills of Materials all the time, though. Gotta get that working. Thanks for the reply! John

Oh - oh! Bills of materials don't seem to work in V5 either. I'll try removing V5 and reinstalling.

Hi! With IronCad 5 it seems the parameters window doesn't open. Anyone else have the same problem? Thank you. John

Good to hear you had the same problem with the Fire GL2's digital-out port (that's a terrible thing to say, isn't it?). I'm using a NEC MultiSync FP1350X, which also has a digital-in port. With the Fire GL2 it results in a very noisy picture, though, so I use it with its analog port. The analog port gives outstanding results, though. I don't know how digital could be better!

I use Fire GL2 as well, in a P4 1.4GHz box with an Ultra 160 SCSI disk. Nice and fast - no problems. Windows 2000. My previous system was a Fire GL1, in a dual P3 550 MHz with Ultra 80 drives. Noticeably slower, especially for large assemblies. For most work it's fine, but becomes unusable for the big scenes with lots of externally linked files. Thanks IronCAD. John