I have seen some of the ultra wide monitors/TV`s on the web , it must be like looking at the world through a letterbox .
nice , but expensive .

My point exactly. 4:3 was ideal for computers. An ultrawide is just two 4:3s together without a gap. That's what they use in hospitals for heart monitors etc. 16:9 is nice to look at for watching a film, or maybe playing a game, but beyond useless for anything like word processing or browsing the internet, where height is more important than width. I can't believe they've stopped making them!

I love 16:9 on my 25 inch, it's better than 16:10 for running 2 programs side by side (or three when troubleshooting logs, webclient and server side) .

So you're basically using it like two monitors. I prefer two monitors. Or an ultrawide which is effectively two 4:3s, it's 16:6.

With the added benefit of being able to use the display as 1 for apps that require more width than half the screen (like SoapUI).

[edit
doublepost :(

I think Dell still makes them.

does .out file in c:programdataboincslots[slot number here]shared change?

Sorry, I didn't see this, but neither do I know what .out file I should look at, nor what slot it was running in, nor know if or how it might've changed.
Task aborted now - I assume the info has gone now?

To find the slot number click on the task in the tasks column, them on properties.

The info is gone shortly after the output files are uploaded and the task is reported as finished.

The probable change to look for is any change to the dates and size of the .out file.

If there is more than out .out file in the slot directory, look for changes in the dates or size in all of them.

Of course, thanks. I'll bear that in mind for next time.
When I get home tomorrow I'll look at my current tasks as well, just for a bit of practice at what I should expect to see

---

you can copy out file twice waiting several minutes between copies and then compare two copies with winmerge

Right. I'd kind of already decided what I was going to do in that particular case, but I'll bear it in mind if there's a next time

---

[edit
doublepost :(

Edit it to contain two space characters and it will vanish.

I think Dell still makes them.

I don't see any here: https://duckduckgo.com/?q=dell+4%3A3+monitor&t=opera&iax=shopping&ia=shopping

I thought you were talking about 16:10 monitors

I thought you were talking about 16:10 monitors

No, I don't recall mentioning them. I like 4:3, or at a push an ultrawide which is two 4:3s.

Dell have always made odd stuff, they used to do monitors squarer than 4:3. 3.5:3?

As with many things ,
just search for it on Ebay ;-)

As with many things ,
just search for it on Ebay ;-)

First place I looked, I used to get second hand 4:3s on there. Now I can only find free ones occasionally on freecycle, I HATE WIDESCREEN! Widescreen is for televisions, NOT COMPUTERS!

There is this 1600x1200 Eizo FlexScan
https://www.amazon.com/Eizo-FlexScan-S2133-BK-Monitor-1600x1200/dp/B00KDMMKD0

There is this 1600x1200 Eizo FlexScan
https://www.amazon.com/Eizo-FlexScan-S2133-BK-Monitor-1600x1200/dp/B00KDMMKD0

A thousand dollars for a 21" screen? What planet do you come from? I have a 20" 4:3 here at that resolution I bought for $60.

I don't know what the problem is, the rosetta units advance in calculation but the load of the cpus remains at zero... as if nothing was calculated...

Tested with Boinc Windows 7.16.20 (x64) with or without VM.

A solution ?

Thanks in advance for the reply.

---

I think you can open virtualbox manager gui and show vm screens and if vm is stuck you can try to reset vm.

I have a Rosetta Python task with a problem I've never seen before.

It's been running (or claiming to be) for hours, but it's still showing no CPU time and no memory used so far.


Application rosetta python projects 1.03 (vbox64)
Name aaam-PHE_pp-mNMVAL-ACPC-AMACBEN2_2_2554686_6
State Running
Received 6/4/2022 6:13:14 PM
Report deadline 6/7/2022 6:13:13 PM
Estimated computation size 80,000 GFLOPs
CPU time ---
CPU time since checkpoint ---
Elapsed time ---
Estimated time remaining 08:00:00
Fraction done 0.000%
Virtual memory size 0 bytes
Working set size 0 bytes
Directory slots/6
Executable vboxwrapper_26203_windows_x86_64.exe


I've decided to let it reach its deadline, then abort it.

I've never checked the memory, but no CPU time is the common bug everyone is getting, just send it back and get on with another. It's not going to be of any use sitting there not using the CPU, you're just wasting a core.

Hey, we're actually nearing the end of the pythons! Hopefully either the next batch will work better, or preferably they won't use VB anymore.

no CPU time is the common bug everyone is getting

Correct.
As soon as you see it happening, don't wait for something to change - it never EVER does.
Abort it on sight every time

---

no CPU time is the common bug everyone is getting

Correct.
As soon as you see it happening, don't wait for something to change - it never EVER does.
Abort it on sight every time

Sounds like an instruction to a soldier.