TurboCAD Forums

The Ultimate Resource for TurboCAD Knowledge

Register
 
The purpose of these forums is to discuss TurboCAD.  Please keep the discussion of other products to compatibility issues or how the other software’s can be used with TurboCAD.


Windows 10
Read 21253 times
January 04, 2016, 10:13:38 PM
#50
I just purchased a Quadro and found out that REDSDK does NOT support the driver! The driver they support is 340.84 released on 2014.9.23, Current driver is 354.56 released 2015.12.9 with Windows 10 support.

A quick check shows REDSDK has no driver support for Quattro M series or any of the M or K series 5200, 4200, 2200 cards

Maybe someone could let REDSDK there is a new version of Windows?

I did Google down a 340.84 driver for Windows 7x64 but it has been my experience with my existing Nvidia SLI cards that the driver REDSDK says works doesn't always.



 

Logged
TurboCad V12~V201x Platinum Pro Edition + CAM Plug-In +  Surface Modeling + Survey Coordinates RedSDK
Production: W10 Pro V 1809 OSB 17763.165 I7 12GB NVIDIA Quadro
TC2019 Test Machine Dual Xeon 16GB W10 Pro V 1809 OSB 17763.165 Nvidia Quadro 416.78


January 04, 2016, 10:44:10 PM
#51
I forget the name (and I'm replying from my phone), but I remember someone here posting about his 2200 (if I remember correctly) and how he is quite happy with it.

Try to search for the posts where he talks about it and see if he responds to a private message.


Jeff

Logged
TC Pro Platinum 2018, 2017, 2016 & 2015 (all with LightWorks & RedSDK) & V21
System: i7-5820K @ 3.30GHz, ASRock X99 Extreme4, 16GB DDR4-2133 RAM, Gigabyte GTX 970, Samsung NVMe SSD 950 (256GB), Windows 7 Pro (64-bit) SP1


* January 05, 2016, 08:27:15 AM
#52
You can rewind to the previous operating system.  Maybe you should do that, copy your data files elsewhere and try again.

Thanks for the heads up, though.


Jeff

Be Aware, there are 3 hidden files in Windows 10 that stop working after the 30 day trial. Now you're stuck with v10.

Logged
DonCW

2017 Platinum
Light Works Plug in
Windows 10
There's so much to learn and not much time left to learn it.


* January 08, 2016, 07:30:39 AM
#53
Antique here. Retired, using pro 14 and just upgraded to win10. Unable to open tcw files, reinstall tp14 and able to open a few more files. I've chosen to save what I can to dwg so I hope I can access no matter what.

Logged


* January 08, 2016, 03:38:15 PM
#54
I just got a turbocad 2015 deluxe 2d/3d and have a new laptop upgraded to windows 10. I still have not installed it yet, any thoughts if they work?

Logged


* January 08, 2016, 09:24:44 PM
#55
I just got a turbocad 2015 deluxe 2d/3d and have a new laptop upgraded to windows 10. I still have not installed it yet, any thoughts if they work?

If you have not purchased the lightworks plug-in with 2015, then the main issue with 2015 and windows 10 would be if the graphics card / adaptor is compatible with RedSdk, though the actual program will (should) still work even if its not,  you can check out the graphics card here (I didn't do any extensive render tests with my incompatible card, just tried the program itself).
http://www.redway3d.com/supported-gpu-tables-for-redsdk/gpus-list-for-the-latest-redsdk-release/

Whilst a few people have had problems, I think the majority who post here are fine using 2015 with windows 10. 
« Last Edit: January 08, 2016, 09:31:49 PM by Andy H »

Logged


January 09, 2016, 01:49:05 PM
#56
The best thing you can do is:

Make a system image of your current OS before you Up?grade to Windows 10 if you really think you need/want the new bloatware spyware ridden offering.

Regards
Bob

Logged
TC 14 Deluxe, TC 19 Pro
Windows 7, 64bit 8GB Ram


January 09, 2016, 01:50:59 PM
#57
The best thing you can do is:

Make a system image of your current OS before you Up?grade to Windows 10 if you really think you need/want the new bloatware spyware ridden offering.

Absolutely the best way to go for this sort of thing.


Jeff

Logged
TC Pro Platinum 2018, 2017, 2016 & 2015 (all with LightWorks & RedSDK) & V21
System: i7-5820K @ 3.30GHz, ASRock X99 Extreme4, 16GB DDR4-2133 RAM, Gigabyte GTX 970, Samsung NVMe SSD 950 (256GB), Windows 7 Pro (64-bit) SP1


* January 14, 2016, 05:21:29 PM
#58
6 months late, but just in case, because I don't find the topic mentioned anywhere...

Micro$oft sometimes adds rever$e logic to the process:  bootup settings in 8- forward include something called 'fastboot', the effects of which I'm seeing along this thread.

One google quote is short and to the point:

". . . shutdown / bootup in Windows 8 and newer are by default not real shutdowns and bootups, but rather a hybrid "log off and hibernate" kind of thing.  What most folks don't realize . . . is that the Hybrid/Fast Boot logic can cause problems.  For one thing some parts of the system are not freshly restarted, and for another it's (possible) the file system (can) actually be left in a dirty state."

So, this refers to the process of using 'Shutdown' and then restarting, which it doesn't.  It keeps part of your previous kernel session on tap while it recycles other overhead, and it goes fairly quickly if '/fastboot' is on.  It's apples and oranges to the 'Restart' choice, which is now actually the closest to a full down cycle, and therefore quite a bit slower as this thread points out.

Of course, in 7 and previous we were trained to use 'restart' to get back onboard sooner.  Shutdown meant shutdown, and restart never went cold .... sort of the opposite.

My only guess at the MS logic is that most people typically do a 'shutdown' and go to bed.  Then in the morning they 'boot up' and, since it seems to go really quickly, they can conclude the newer OS must be much fa$ter than the old.  Cold-cycling reveals the true footprint of that boot.

To be fair, we understand most of the time the OS keeps everything in order, on balance.  But obviously, it can give your troubleshoot a quick boot.  That preserved kernel session may have driver pointers that are honored according to its previous hardware enumeration.  And then there's Superfetch, by which the OS keeps parts of your most-used programs in RAM, even through a 'warm reboot' (even in win7 [even Prefetcher in XP]).  I'm sure many know this.  The issue is, where is the cold boot, really?

I'm no expert. These things google well, so vet this if it seems useful.  I just want to raise a flag here where troubleshoot happens -especially re vid drivers, because I haven't found any mention and I see threads about doing a cold boot that wouldn't be.  And BTW, for a really complete blankout . . .  you have to disable fastboot, shut down, pull the plug (and battery), and then hold down the power button for 5-10 seconds to bleed it dry.  Only then can you know you've done your best to not track something in on the bottom of your boot. :-[

Best regards,
Lee G


Logged
V21 Plat build 59 x64  / LW / Win7 64; Intel 3000 GPU; 3.1GHZ; 16GB