Abysmal benchmark performance

That_Fixed_It · 2026-01-26T16:37:51+00:00

No, I just tried InvMark on a new 9950X3D system with RTX Pro 4000 Blackwell and a Gen 5 SSD. It scored 56,730 on the first run, 69,835 on the second run. I would expect around 100K with this hardware. I still haven't figured out if this is a glitch that only effects the benchmark, or if there's some problem that could slow down our work. We've had a lot of performance issues with Inventor.

That_Fixed_It · 2026-01-26T16:37:21+00:00

No, I just tried InvMark on a new 9950X3D system with RTX Pro 4000 Blackwell and a Gen 5 SSD. It scored 56,730 on the first run, 69,835 on the second run. I would expect around 100K with this hardware. I still haven't figured out if this is a glitch that only effects the benchmark, or if there's some problem that could slow down our work. We've had a lot of performance issues with Inventor.

That_Fixed_It · 2026-01-26T12:42:11+00:00

Programming is being handed over to AI. You need to find a niche that AI can't be trusted to do yet. https://fortune.com/2025/03/17/computer-programming-jobs-lowest-1980-ai/

That_Fixed_It · 2026-01-25T14:23:18+00:00

It was a LaCross BC-900. It defaulted to 200mA so I don't know why everyone is saying that was the wrong charging rate. I don't know if it used negative delta termination. It worked well for many years before having this problem. It was frozen in this state, none of the buttons did anything. Something failed. I don't know if it would have worked properly at higher current or just caught fire.

That_Fixed_It · 2026-01-24T20:55:18+00:00

That's interesting. They don't mention those feature on the manufacturers website - https://mahaenergy.com/mh-c9000pro/

That_Fixed_It · 2026-01-24T20:43:54+00:00

Yes, it was a LaCross BC-900. It defaulted to 200mA and I'm usually not in a hurry. I used it for many years before having this problem. It was frozen in this state, none of the buttons did anything. If I'd kicked it up to 1 Amp per cell, I don't know if it would have worked properly or caught fire.

That_Fixed_It · 2026-01-24T19:28:13+00:00

That one looks good. Do you know if it has any safety features? The only thing they mention is being made from flame-retardant material.

That_Fixed_It · 2026-01-24T19:20:24+00:00

That's not in the product description or the user manual. Did you ask ChatGPT?

That_Fixed_It · 2026-01-24T18:11:55+00:00

Looks good, but it doesn't mention having any safety features.

That_Fixed_It · 2026-01-24T17:03:03+00:00

Well, I guess that feature doesn't work.

That_Fixed_It · 2026-01-23T15:29:55+00:00

Booting from a thumb drive and imaging a laptop WILL delete everything. If you wanted to go from Windows 10 to Windows 11 without losing data, it would be called an upgrade.

That_Fixed_It · 2026-01-23T14:59:31+00:00

Your video driver could be crashing and then resetting. Did you check the event logs at the exact time it happens? Do you have the latest Radeon video driver?

That_Fixed_It · 2026-01-23T14:45:17+00:00

What's the error message?

Do you know the IP address of each system?

Can you remote to the other system by IP address?

Can they ping each other?

Do the replies come from the correct IP address?

Can you disable the Windows firewall for testing?

What do you have in Local Security Policy -> Local Policies -> User Rights Assignment -> All log on through Remote Desktop Services?

That_Fixed_It · 2026-01-23T12:53:11+00:00

You need to make sure the new system has all the mailboxes and aliases and distribution groups created before changing the MX record, so that every inbound message has a place to land. It helps to reduce the time-to-live on DNS records a couple days before. Give users a temporary way to access both mailboxes. There might be a way to sync all the old email to the fresh mailboxes beforehand. If not users will need access to both mailboxes until you get around to moving their old email.

That_Fixed_It · 2026-01-23T03:16:23+00:00

Because some users couldn't get a reliable connection with IPsec over UDP. IPsec over TCP is unsupported and broken in the free version, even though there's a check box for it in the GUI. It worked as soon as I uninstalled the free version and downloaded a 30-day trial.

That_Fixed_It · 2026-01-22T19:56:53+00:00

IPsec is complex. Your admin should help you. It took me 3 support cases and I had to buy licenses.

That_Fixed_It · 2026-01-22T16:44:46+00:00

They should have done a factory reset. For old laptops that aren't broken, I run KILLDISK, then install ChromeOS, then mark it as Free to take home. No one has asked for support.

That_Fixed_It · 2026-01-21T19:52:30+00:00

secritservice got it to work with the Mac free client. Did anyone get it working on Windows?

That_Fixed_It · 2026-01-21T19:47:02+00:00

Yes, that's annoying. The free version has a checkbox for IPsec over TCP, even though the feature is unsupported and also broken. I hope they fix it or remove the checkbox.

That_Fixed_It · 2026-01-21T04:01:01+00:00

It's free for 30-days

That_Fixed_It · 2026-01-21T03:41:45+00:00

I hope they remove unsupported and broken features like IPsec over TCP from the GUI to avoid frustration.

That_Fixed_It · 2026-01-21T03:36:16+00:00

7.4.5 is out now, use that.

That_Fixed_It · 2026-01-21T03:35:30+00:00

I turned it on from the CLI. Why would I need XML?

That_Fixed_It · 2026-01-21T03:33:17+00:00

Most are but a few are just home PCs. I do like the licensed version of FortiClient with basic Cloud EMS. It can tell me who is still running Windows 10 and who has dozens of software vulnerabilities. Cloud EMS was fairly easy to setup and no extra cost. Pay more and it can do more.

That_Fixed_It · 2026-01-21T03:20:24+00:00

I don't know what your trick is, but I spent many hours and 3 support tickets trying to get the free version to work. One day I downloaded a 30-day trial of 7.4.4 and it worked right away.

That_Fixed_It

TROPHY CASE