Differences

This shows you the differences between two versions of the page.

--- home_server:mswindows_notes [2025-12-01 Mon wk49 13:22] – [TOC (Table of Content Switches] baumkp
+++ home_server:mswindows_notes [2026-01-29 Thu wk05 06:29] (current) – [XREF Layer control] baumkp
@@ Line 1: / Line 1: @@
 {{tag>mswindows windows setup tip notes personal license powertoys}}
-======KPTree - MSWindows Setup======
+======KPTree - Home Desktop Setup======
 =====Background=====
-I have Windows on my main desk top machine, it is dual boot with Debian/XFCE.  I am using Debian almost exclusivly now.  The BIOS based dual boot works well, I have it defaulting to Debian.  I do not currently have a Windows VM setup on my main server.  My 3 sons also have computers with Windows on them. Lastly, I am required to used company Windows machines at work.  Hence I like to keep a list of my preferred Windows software reasonable up to date.
+I have Windows on my main desk top machine, it is dual boot with Debian/XFCE.  I am using Debian almost exclusively now.  The BIOS based dual boot works well, I have it defaulting to Debian.  I do not currently have a Windows VM setup on my main server.  My 3 sons also have computers with Windows on them. Lastly, I am required to used company Windows machines at work.  Hence I like to keep a list of my preferred Windows software reasonable up to date.
-I have been using Microsoft products for quite some time, starting with MSDos then Windows 3.0, 3.1, 95, 98, XP, 7, 8, 8.1 and finally 10. (I managed to skip some of the duds, such as ME, 2000 and Vista, although I did occasionally use them on friends, family and work machines. Contrary to all the noise I never had any problems with version 8 & 8.1. I thought ME was bad and Vista too, but as noted basically managed to avoid them in the most part.)
+I have been using Microsoft products for quite some time, starting with MSDOS back in the 80's then Windows 3.0, 3.1, 95, 98, XP, 7, 8, 8.1, 10 and finally 11. (I managed to skip some of the duds, such as ME, 2000 and Vista, although I did occasionally use them on friends, family and work machines. Contrary to all the noise I never had any problems with version 8 & 8.1. I thought ME was bad and Vista too, but as noted basically managed to avoid them in the most part.)
 ++++tldr; Old build|
 Recently my main home office machine failed. I build this computer myself. Basically originally an Intel i7 with the built-in graphics and a 2TB HD, 32GB RAM (16GB would have been enough) and of course a Seasonic 80plus gold power supply. I then quickly replaced with a 500GB SSD, by this time I had my Linux home server running and used this as a NAS for bulk storage and serving. When I set the machine up it was based upon Windows 7 (64bit of course). When Windows 8 came out I upgraded, then Windows 8.1 and finally Windows 10. A few years later I added a Nvidia 960 graphics card, to help breathe a bit of extra life into the machine (and play games better....) I have tried quite a large amount of software on this machine over the period and it was somewhat cluttered, albeit I did run the likes of CCleaner and SystemMechanic to help keep it usable. In any case I tried to load AutoCADLT 2017 on the machine (yes, a licensed version, my being a professional engineer) it worked on the first evening after loading, then the following day ACADLT stopped working. I tried to get it working to no avail and attempted a reinstall, also to no avail. The following day the machine would not run with the dreaded blue screen of death. Nothing I attempted would revive it. So I investigated a clean Windows 10 install. I downloaded a Windows 10 recovery / installation on to a USB. Turns out product code is no longer required, and my registration for this machine is tied to the hardware and my Microsoft account. After this reinstalling Windows 10 was a breeze. My original install was totally shot. Hopefully I did not have any important information left on the local documents directory. Unknown, unlikely, but possible. Helps to have the Linux NAS and Nextcloud working. It is also a reminder to do my NAS and Nextcloud backups. I got to keep on top of this, and need to try to do it every month.
-My son got my old machine and I upgraded to a new Intel i9, with 1TB NVM SSD and 16GB RAM. Of course with a Seasonic 660W Titanium power supply. My first water cool CPU, which has been working a treat!. No graphics card yet, would like to get one in the next year or so.  My youngest son got this machine in early 2022. I got a new Intel i9 NUC, which I got with 32GB or RAM and 2TB NvME.  I am currently using the built-in Intel graphics, but the NUC will allow a lower tier full size graphics card to be installed (graphics cards is primarily limited by 2 bay size, 650W power supply). ++++
+My son got my old machine and I upgraded to a new Intel i9, with 1TB NVM SSD and 16GB RAM. Of course with a Seasonic 660W Titanium power supply. My first water cool CPU, which has been working a treat!. No graphics card yet, would like to get one in the next year or so.  My youngest son got this machine in early 2022. I got a new Intel i9 NUC, which I got with 32GB or RAM and 2TB NvME.  I am currently using the built-in Intel graphics, but the NUC will allow a lower tier full size graphics card to be installed (graphics cards is primarily limited by 2 bay size, 650W power supply).
+The old build from 2011 became very unreliable and was finally fully upgraded in 2025 to the current Intel i5 CPU at that time, with 48GB RAM.  I used the NVidia 2060 in this machine for one son.
+The old build from 2016 was upgraded in 2023 to a current Intel i% at that time, with 32GB RAM.  I use an Intel ARC A770(?) graphics card.
+The old 2018 build is currently in disrepair as the son spilled Coke drink on it and it became unreliable and finally fail.  The Nvidia graphics card was not doused in Coke and was repurposed as noted previousl. This son got a current 2025 Intel CPU laptop as a replacement and has not got a desk top at the moment.  I recently asked for a replacement desktop (for gaming), however as of writing 2026 Jan there seems to be a supply demand imbalance in the industry and all computer pricing has increased enormously in the past 6 months.  Further to this Intel just announced their latest CPU range that looks like a significant improvement worth waiting for. (I was seriously thinking given AMD another try, after a bad experience in 2011 on my first home server build.)  I also probably need to upgrade a couple of graphics cards the Nvidia 2060 getting long in tooth and needed a new card if I make a new build.  Graphics cards are also excessively expensive now.
+++++
 So below is a list of Windows software often use.
@@ Line 58: / Line 64: @@
   *Productivity (Unless otherwise noted the software I use at work provided by work. I believe it to be appropriately licensed by work too.)
       *ACadLT2017 - CAD - got rid of this subscription, just too expensive for my occasional use.
-      *ACAD 2022 - CAD software I use at work.
+      *ACAD - CAD software I use at work, uses a network token system on the latest loaded version.
       *Navisworks - 3D productivity software, I started using the limited free, version at work, Freedom.  I now have the full version at work, Manage.
       *Foxit Pro - a PDF reader and writer (**!**) I no longer use, there is no full Linux that I can use on my home machines.
@@ Line 445: / Line 451: @@
 ====STYLEMANAGER====
 The command ''STYLEMANGER'' opens up the directory where the plot styles are stored.  Different plot styles can be copied to and from this directory.
+====Line Weights====
+''LWEIGHT'' opens Lineweight Setting dialog box
+  *''LWDISPLAY'' set to 0 (off) will hide display lines weight, set to 1 (on) will display line weights.
+  *''LWDEFAULT'' changes the default line weight size.
+    * 0 will use thinness line supported by printer.
+    * Otherwise, line thickness set to hundredths of millimeters, values from 0 - 2540 hundredths of millimeters.
+  *''CELWEIGHT'' sets line weight of new objects:
+    * -1, Sets the lineweight to "BYLAYER." (Default).
+    * -2, Sets the lineweight to "BYBLOCK.".
+    *-3, Sets the lineweight to "DEFAULT."  Where "DEFAULT" is controlled by the LWDEFAULT system variable.
+    * Other valid values entered in hundredths of millimeters, from 0 to 2540 hundredths of millimeters.
+====XREF Layer control====
+Issue: Changes to an External Reference (Xref) do not show up when reloading the Xref in AutoCAD products. Such changes include:
+  *Layer line type.
+  *Layer line thickness.
+  *Layer color.
+  *Layer transparency.
+  *Elements added or deleted.
+  *Additionally, the Xref may update in the base drawing without issue when a different layer with the same properties is chosen.
+Causes:
+  *The ''VISRETAIN'' system variable is set to 0.
+  *The ''VISRETAIN'' system variable is set to 1 and the VISRETAINMODE system variable is set to 0.
+  *''XREFOVERRIDE'' is set to 1.
+  *Corrupted file.
+  *Corrupted AutoCAD profile.
+  ***Changes are being made in paper space**
+''VISRETAIN''
+^Value ^Descritption ^
+|0 |The layer table, as stored in the reference drawing (xref), takes precedence. Changes made to xref-dependent layers in the current drawing are valid in the current session only and are not saved with the drawing. When the current drawing is reopened, the layer table is reloaded from the reference drawing, and the current drawing reflects all of those layer property settings.|
+|1 |Xref-dependent layer changes made in the current drawing take precedence. Layer settings are saved with the current drawing's layer table and persist from session to session. **(default)**|
+''VISRETAINMODE''
+Controls the behavior of the VISRETAIN system variable when it's set to 1.
+Use this system variable in conjunction with the VISRETAIN system variable to control which xref layer properties that you want to automatically sync on reload.
+Note: Xref layer properties with overrides are not synced when the xref is reloaded. To clear any overrides, use the shortcut menu option, Reset Xref Layer Properties For, on the Layer Properties Manager.
+^Value ^Description ^
+|0 |No settings are synchronized. You will have the same experience when you set VISRETAIN to 1 in AutoCAD 2017 or earlier.  **(default)**|
+|1 |On/Off synchronized. |
+|2 |Freeze/Thaw synchronized. |
+|4 |Lock/Unlock synchronized. |
+|8 |Plot/No Plot synchronized. |
+|16 |Color synchronized. |
+|32 |Linetype synchronized. |
+|64 |Lineweight synchronized. |
+|128 |Transparency synchronized. |
+|256 |Plot style synchronized. |
+|512 |New VP Freeze synchronized. |
+|1024 |Description synchronized. |
+To specify more than one layer property to sync, enter the sum of the bitcode values. For example, a value of 3 specifies that both the On/Off (1) and Freeze/Thaw (2) layer properties will automatically sync when the xref is reloaded.
+''XREFOVERRIDE''
+Controls the display of object properties on referenced layers.
+The XREFOVERRIDE system variable affects display and plotting, and works in conjunction with the VISRETAIN system variable. If you want the xref layers to retain their original layer settings, it is recommended to set VISRETAIN and XREFOVERRIDE system variables to 0.
+^Value ^Description ^
+|0 |When the properties of the objects (such as color, linetype, lineweight, transparency, or plot style) on the external reference drawing are set to ByLayer, any changes to the xref layer properties are displayed in the current drawing (legacy behavior) **(default)**|
+|1 |When the visual properties of the objects on the external reference drawing are not set to ByLayer, objects on xref layers are treated as if their properties are set to ByLayer and every external reference layer can have its own set of layer overrides |
+Note: The XREFOVERRIDE system variable only applies to DWG xrefs, not to other references such as underlays.
+**References**
+  *Autodesk:
+    *[[https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/Modified-xref-layers-are-not-updating-with-Reload.html?msockid=3252c0c437986e992b7dd21936096f31|Modified Xref layers do not update in the host drawing when the Xref is reloaded in AutoCAD products]]
+    *[[https://help.autodesk.com/view/ACD/2023/ENU/?guid=GUID-897B1672-4E09-42E0-B857-A9D1F96ED671|VISRETAIN (System Variable)]]
+    *[[https://help.autodesk.com/view/ACD/2023/ENU/?guid=GUID-46480687-6DFF-499E-B7C0-E741AEA11D00|VISRETAINMODE (System Variable)]]
+    *[[https://help.autodesk.com/view/ACD/2023/ENU/?guid=GUID-131E3BBB-A28A-40BC-BDC5-A4486C1E2DBE|XREFOVERRIDE (System Variable)]]
+    *[[https://help.autodesk.com/view/ACD/2025/ENU/?guid=GUID-DEB2A4C9-8C16-4EC9-8392-1BF8ED2A383A|Layer Settings Dialog Box (Layer Properties Manager)]] LAYER (Command) {{:home_server:guid-17e48045-1f9a-4b8d-b2de-01b2b8da4c4e.png?24|}}: Layer Settings {{:home_server:guid-742d2bd9-aa09-4ec4-8860-86a56e7bea7a.png?24|}}
+    *[[https://help.autodesk.com/view/ACD/2025/ENU/?guid=GUID-B297EBD9-D68C-47E1-87CE-1B3798496599|Layer Properties Manager]] LAYER (Command) {{:home_server:guid-17e48045-1f9a-4b8d-b2de-01b2b8da4c4e.png?24|}}
+  *[[https://www.howtoautocad.com/visretain-xrefs-not-saving-layer-states|VISRETAIN - Xrefs not saving layer states]]
 ======Accessibility Contract Checker======
 Form versus function, unfortunately the moronic types seem to favour form over function.  Contrast of text is particularly important to allow easier reading.