I would suspect that extra 10GB is "reserved storage"; it seems to be in the right ballpark for size -The attached jpeg shows one of the file sys problems I’ve encountered (why Win10 is using an extra 10gB on a USB drive concerns me, telemetry?)
Thanks Hippy, That sounds very likely. Hope it doesn’t reserve 10gB on a 16gB Flash drive (that could cause some comedy).I would suspect that extra 10GB is "reserved storage"; it seems to be in the right ballpark for size -
I don't know. If it's a bootable drive then it perhaps could. I recall it caused some problems with Win 10 systems and tablets that were using smaller SSD's.Hope it doesn’t reserve 10gB on a 16gB Flash drive (that could cause some comedy).
I've sworn off those ever since I picked up a Mini-PC with just 32GB and no DVD drive. After however many hours of it trying to update, it ended with a "something went wrong" error and just an "OK" button.
When I read broad-brush statements like that, it tells me more about the sender than the receiver. (Of course, not implying Hippy said it.)"The fear has always been that this meant Microsoft would start charging users a monthly fee to maintain the operating system, and now a new leak has confirmed this is exactly what will happen"
I'm gonna guess the file history service is enabled to keep previous versions of your files. It's a nice feature for having the capability to restore files that got accidently overwritten/corrupt/encrypted with ransomware, but sucks when you're already running low on disk space. Check the Control Panel / File History to see if it got enabled.(My hard drive has ~700gB left, so don’t know why Win10 needed to reserve 10gB on my little flash drives)
It seems most software is moving toward the subscription model. I see the possibility of Windows 10 becoming available "free of charge" but with advertisements. Or you can pay a monthly fee of $5-9 to remove the ads. Either way, MS wins with the telemetry.Anybody wanna' prognosticate? Might be fun to take a guess on the future.
Unfortunately it is not as simple as it sounds, and is even more complicated for a Raspberry Pi which is ARM-based, rather than X86.
The only way to find out is to try it, but that should be easy enough for someone who has an X86 Linux system.Wonder if PE6 will run under this version?
That is good news. Mac OS is Linux at its heart so what works for Mac should also work for Linux, though there may be slight differences in the installation process.I do now have the PE6 editor installed, under Wine on my Mac running OS X (10.9).
I created a WineSkin, used as you suggested, WineTricks to install DotNet35sp1 and MFC40 (which I did before) and (crucially!) GDI+. This got me up and running. Programs load, compile and simulate.
That might be possible to solve. Linux can be a bit picky and Mac more so, so it may just be a matter of finding the right settings and incantation to use.I never got programs to download as the USB cable was never seen by WINE, no matter how I tried.
Catalina, or more Apple's decision to not support 32-bit, is a PITA. How absolute that is remains to be seen. If there are means to emulate or run virtual machines under Catalina it might be possible to get MacAXEpad, LinAXEpad, WinAXEpad or PE6 to run under Catalina.Unless I really needed the simulation features I would always use AxePad instead. That's come to a halt with macOS Catalina dropping 32bit support. No PicAxe programming for now!
Any helpful hints on how to install ?It will install but won't run.
I made sure I had wine 5.xx [wine --version]Any helpful hints on how to install ?
Seems I had "Wine-4.0 (Debian 4.0-2)" which appears to be the latest 'apt-get install' package available for Debian Buster (stable).I made sure I had wine 5.xx [wine --version]
WINESkin seems to be a Mac only thing which doesn't exist for Linux so I guess we need to find an equivalent for Linux or discover how to do it with WINE itself.I succeeded by 'cheating'. I use WINESkin to create the WINE environments
What you are seeing in your screen-shot appears to be exactly what I am seeing.I followed your link and gave PE5 a go.
I suspect that it doesn't matter apart from when interacting with it from within a Linux/Mac command shell. WINE should be able to handle the fact that files on disk may have a different case to what's been specified and deal with that.I don't have the MFC file but found the .ocx one. By the way, is it MFC or mfc?
For a real Windows system it would be "regsvr32 \windows\system32\wave32.ocx' from the 'MS-DOS Prompt; or something like that. But not sure how that should be done for WINE - Perhaps one needs to install CMD.EXE under WINE, run that, and enter the command ?I don't know what "registering" involves.
[kl@PB system32]$ wine regsvr32 wave32.ocxI'm not sure though what the focus is on 'mfc40.dll'. As can be seen, PE5 starts-up okay, runs, and doesn't complain about any lack of 'mfc40.dll'.