jmmilner

It took some time and a bit of AI (Gemini in this case) but the issue with Windows 10 turned out to be ASLR - Address Space Layout Randomization. Once I turned this "feature" off for the Chief Architect EXE file, the issue disappeared. The following shows the changed setting - first search for "Exploit protection" to find this tab: I'm still working on the problem for Windows 7 and 11 but as the Windows 10 machine is my triple monitor 14700K primary desktop, I'm largely back in business. TL:DR Address Space Layout Randomization is a technique used to combat various exploitations that depend on knowing the exact location of a program's code, data, and/or stack. It works by scrambling (randomizing) where these are located each and every time the program is run. The exploit can guess or try other methods to compute where the code or data they want to attack is located, but the odds aren't in their favor. Apparently whoever coded the Layers tab of the Wall Specification also depended on knowing how the data was laid out, which at one time (long ago) passed as cleaver. In the process of making this change, I also discovered that Acrobat.exe and assorted friends actually forced this feature on for their executables - likely because, unlike a niche program like CA, Acrobat is ubiquitous and therefore a prime target for exploits.

I do something similar with a TrueNAS Community Edition 25. In my case the two PCs are a Windows 10 desktop with triple monitors for real work and a Windows 11 laptop for on-site or out of town work. The magic to get both machines to appear to be on the same local network is Wireguard, but otherwise the setup mirrors yours. On both machines the NAS directory containing my CA files is mapped to a drive letter in Windows. As far as CA knows, it is just like another hard drive or flash drive. There are plenty of tutorials on the web as to how to setup the mapping. Basically Step 1: Open File Explorer. ... Step 2: Click on "This PC" ... Step 3: Click on "Map Network Drive." ... Step 4: Choose a Drive Letter. ... Pick a letter near the end of the alphabet Step 5: Enter the Folder Path. ... Something like \\NAS_box_name\\CA_directory Step 6: Optional Settings. ... Step 7: Finish the Setup. As long as you are the only user and can only open CA on one machine at a time, there isn't much risk of multiple copies getting out of synch.

Was updating a simple 2D drawing of a possible kitchen renovation for a family member. Not sure why but when I opened a wall specification I clicked on the Layer tab and bang: Assertion failed! Program: ...10.0 Full Version\Chief Architect 10 Full.exe File: .\source\walldlg.cpp Line: 3309 Expression: convertHdl != NULL && viewSceneHdl 1= NULL For information ....Visual C++ .. asserts The three options, Abort, Retry, and Ignore all cause an immediate crash to the desktop. At first I assumed I'd messed up the model in some fashion but, starting from a blank plan, drawing a single wall, and selecting the Layers tab of the Wall Specification dialogue produced the same results. Even opening one of the sample plans that came with CA, in a new instance of the program, ended the same way. After all manner of fooling with Windows 11 settings, I when back to Windows 10 and then to an old Windows 7 machine and it happened on both. Before I spin up a VM or dig out an even older PC, can somebody please repeat the single wall test and tell me if I'm alone? The attached JPG shows my test case on a Windows 10 Pro machine (i7-14700K, 32GB, RTX 5070, 2TB NVMe):

I too can confirm that Bob's method works! Like many here, I've been getting by just fine with CA10, as I'm more of a retired user whose needs and budget, never mind the learning curve, can't justify newer versions. Over the years I've stumbled and bumbled my way to getting CA 10 to run on Windows 7 and Windows 10 as I upgraded my hardware. When it came to moving to my new machine this summer, the HASP lock drivers I'd squirrelled away that had worked before seemed to have failed. I when so far as to compare the drivers across my collection of XP, 7 and 10 machines, file by file and version number by version number, but couldn't find a difference that stopped me this time. For me the key was Bob's mention in passing that the newer driver packages needed to work with newer versions of Windows would not work on a fresh install of CA 10 from the original media. The key was applying the 10full08b_h.exe update to Chief - it takes changes in that package to enable good old CA 10 to speak to the more modern (?) versions of the HASP Windows drivers. Then it is just working around Windows' reaction to the signing certificate ART used 20 years ago having expired - hence the big red box.

Overthinking is one of my core competencies! I got all hung up trying to build a foundation room under the porch and messing with those settings. The Room Specification did exactly what I needed instantly. Thanks for the quick response.

Title says it all. I have a complete plan with an existing foundation, first and second floors, plus complex roof. The plan represents the current state of a rehabilitation of an 1860s farm house that was built in three phases. The house was raised and a complete new 9' poured concrete foundation unifies the three prior foundation sections. All good. Now the owner wants to add a covered porch across the front that works with the existing two story section yet merges with the roof line of the one story portion of the home. I think I have managed that but the last twist has baffled me - how do I arrange things so the porch floor/deck level is a step down from the first floor which is at relative elevation 0? I've included a screen shot of the exterior with the porch at the same level as the first floor. Any suggestions? 1860 draft65a.pdf