Sujet : Re: encapsulating directory operations
De : mutazilah (at) *nospam* gmail.com (Paul Edwards)
Groupes : comp.lang.cDate : 20. May 2025, 16:28:39
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <100i73b$2a4q9$1@dont-email.me>
References : 1 2 3 4 5 6 7
User-Agent : Microsoft Outlook Express 6.00.2800.1106
"Richard Heathfield" <
rjh@cpax.org.uk> wrote in message
news:100i5hm$29du3$2@dont-email.me...On 20/05/2025 15:48, Paul Edwards wrote:
>
<snip>
>
My main development machine/environment is Windows 2000
Would everybody please close their eyes and bow their heads?
It's also capable of running Visual Studio 2005, which means
I can target x64 processors, even though I can't run the
executables themselves. Although I will normally use cc64
as my x64 compiler, which I can also run as a 32-bit program.
I expect to investigate mm64 one day, but still have other
priorities.
I don't often need to run x64 executables, but when I do, I
copy them to my Windows 10 system, that Windows 2000
is running under.
And here are my size constraints:
2025-05-14 06:15 AM 20,401,095,168 win2000.vhd
2025-05-14 06:15 AM 19,327,353,344 pauldata.vhd
I think my Pinebook Pro was 64 GB storage.
If I give up Visual Studio 2005, I can reduce the win2k
down to about 4 GB I think, meaning I can cope with
a 32 GB storage machine.
Note that the VHD can be mounted on Windows 10
natively, but I don't currently need to do that. I instead
have a shared folder c:\w2kshare on my Windows 10
system, and something from Virtualbox installed on
the w2k system so that I have a Z drive.
I'm officially "apocalypse-ready". The Zhaoxin processor
will make me Last Man Standing if I backed the wrong
horse.
BFN. Paul.