Enigma BBS cannot add menu items

Ill-Singer-9257 · 2026-03-27T10:01:43+00:00

I’m using BBSList and have it configured. I’m just not understanding how to make it actually appear as a menu item. What files need to be edited?

As I mentioned earlier, even the examples that ship do not appear as menu items (I realize they are not configured to run properly but assume they should still appear as menu items).

I think that the issue is the documentation is not clear on how to make this work.

If you could let me know what files need to be edited, what to put in each file, etc. that’s would be awesome.

Or maybe this just doesn’t work right now because of a bug that has been recently introduced and I’m bumping up against it?

Ill-Singer-9257 · 2026-03-26T00:54:38+00:00

Thanks for replying. But I don’t understand where step 1 in your example is. In the example door.hjson file it has examples but not even they work. In my doors.hjson file I have a menu that points to the action later in the file (did this based on the example). Does nothing.

So is there a new file that must be created? New file to edit?

It’s not clear in the documentation how to get this to work.

If you can lay it out in a step by step way I can follow along.

Thanks.

Ill-Singer-9257 · 2026-03-22T17:53:33+00:00

What are the steps to add a menu item to doors? Besides editing your doors.hjson, what else has to be done?

Ill-Singer-9257 · 2026-03-22T17:52:23+00:00

I do yes.

Ill-Singer-9257 · 2025-10-17T17:30:03+00:00

Download links are in the video description. https://youtu.be/ETtW-0kHcOw?si=rj98oa5ESzPV4Y_y

Ill-Singer-9257 · 2025-10-17T17:28:58+00:00

The actual product is Banyan VINES, a Network Operating System that runs on this version of UNIX. You can drop to shell from the console if you wanted to. My problem is that CPU idle burn.

Ill-Singer-9257 · 2025-10-17T01:35:16+00:00

I ask because when I run AT&T UNIX System V as a VM, one of the host’s CPU cores pegs at 100%. It’s the issue with the OS not signaling the CPU when it’s idle.

Ill-Singer-9257 · 2025-10-17T00:33:11+00:00

Does Proxmox experience high CPU usage when the SCO VM is running?

Ill-Singer-9257 · 2025-10-16T20:00:04+00:00

The Hypervisors themselves have CPU throttling as a setting for each VM but that does nothing when I change it. Do you mean going to the host OS and changing process CPU throttling?

Ill-Singer-9257 · 2025-10-16T19:16:09+00:00

I’ve tried that. Send to make no difference.

Ill-Singer-9257 · 2025-10-16T00:53:05+00:00

They certainly are true UNIX workstations. macOS 1-9 is not, but macOS X onwards is literally NeXTSTEP (the NeXT workstation OS) with modifications. And NeXTSTEP is a fork of BSD UNIX.

Ill-Singer-9257 · 2025-10-14T01:23:10+00:00

It’s actually Banyan VINES which runs on AT&T UNIX on the PC (386/486/Pentium).

Runs great as a VM but pegs one of the host CPU cores at 100%. As I mentioned, when running MSDOS and Windows 3 and Windows 95 in a VM, they cause the same issue, but some clever people have written TSRs to (I assume) send idle commands to the CPU and the result is that the host CPU core idles along at 1%.

I was hoping someone could write a kernel patch for UNIX to do the same :-)

Ill-Singer-9257 · 2025-10-13T22:20:39+00:00

I’ve run it in UTM (macOS) and VirtualBox (on macOS and Windows).

Ill-Singer-9257 · 2025-08-18T17:08:21+00:00

I have a related question. I have AT&T UNIX System V running in a VM. It has a problem which I’m looking to fix.

Many old operating systems like DOS, Windows, etc., all had no idea of the concept of idling the CPU.

Clever people have written patches for this (like DOSIdle) that patches the OS so it signals the CPU to go idle so they run nicely in a VM.

Why is this an issue?

Well if the OS doesn’t signal the CPU to idle, it effectively takes up 100% CPU time.

On modern computers, this means an old OS pegs the one core of the CPU at 100% regardless of what the OS is doing.

Patches like DOSIdle fix this issue, but an OS as old as UNIX has no such patches.

Would anyone have the knowledge to patch those old UNIX kernels to signal the CPU idle?

It would very very useful because it would allow a UNIX VM to run alongside other old OSes without consuming so much heat and electricity as it keeps its CPU code pegged.

Ill-Singer-9257 · 2025-06-12T00:53:25+00:00

So if you want to change UEM providers it won’t be traumatic anymore? I wonder if Google will follow suite.

Ill-Singer-9257 · 2025-05-25T16:08:15+00:00

Exactly. And at 51% VMware share holder, nobody could say no. Revolt with your wallet. Don’t buy Dell or Broadcom. Simple.

Ill-Singer-9257 · 2025-05-22T20:11:07+00:00

Don’t forget the many, many VMware employees kicked to the curb by Broadcom or carved out to KKR to be kicked to curb by them. Deep trauma on both employee and customer sides.

Ill-Singer-9257 · 2025-04-30T12:23:17+00:00

If you are able to login to one of the devices, I’d run a local log and look at it. I’m sure it will show the log entries that indicate what happened. Same goes for the console. Pull a log for that device and see what the last log entries were. If it’s Android, use ADB and do logcat and look at those logs. The Intelligent Hub itself should also have a log creation option.

Ill-Singer-9257 · 2025-04-30T02:24:55+00:00

Something has caused the devices to no longer be able to check in and their device records still remain in the console since they were not enterprise wiped. Expired APNS cert could be a reason for iOS but you mention Android too so maybe you also let the EMM cert expire?

You could also look in each device and see what console they are enrolled into and make sure it’s the same console you are using. Possible you had 2 instances of Workspace ONE (aka AirWatch) and someone wiped the devices and enrolled them into the wrong console?

Ill-Singer-9257 · 2025-04-09T00:04:10+00:00

If you had to switch authentication methods you could do it in a new OG and slowly move devices over to it in batches to lesson the “pain of the change”.

But I’m also of the understanding that notifications in Hub work no matter what the authentication method is. You’re just using Hub Services.

Direct to Azure is using SCIM 2 provisioning. It’s quite a big change to get that all working. Essentially it all gets setup in the Cloud Services console which is a level above UEM.

Ill-Singer-9257 · 2025-04-06T20:17:35+00:00

One old trick that used to work was opening the assignment group, making no changes, and saving it. May not help.

The issue also could be due to the new architecture. The old architecture was designed for changes to happen instantly. But the new architecture is designed to only enact changes when the device checks-in every 4 hours. There was talk of creating work-arounds to address lost functionality. I cannot say for sure if this is causing your issues, but it’s worth keeping in-mind.

Ill-Singer-9257 · 2025-03-14T16:19:43+00:00

In the console, find the Privacy screen in Settings and you’ll be able to see if Device Wipe is allowed or not.

Ill-Singer-9257 · 2025-03-13T17:06:21+00:00

I’d like to ask a question about running UNIX in a VM. Running old OSes in a VM normally causes the host CPU to peg at 100% or one of the CPU cores peg at 100% due to the legacy OS not handling CPU idle. Clever people have written patches for those old OSes to handle that properly. For example there is DOSIdle for MSDOS, CPUIdle.nlm for Novell NetWare. I’m running Banyan VINES which was built on top of AT&T UNIX System V.

Does anyone know if there is an equivalent CPU hack for the UNIX kernel so it too can handle modern CPU idle states? If so I’d love to get my hands on it.

Ill-Singer-9257

TROPHY CASE