|
Probably. I'd be okay with basic issues. But *Microsoft* is the one releasing this stuff, and it's like there is zero coordination going on. Hmmm, maybe instead of bitching I'll figure it all out and write an article.
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
|
Well to wrap this issue up, I still am willing to call Microsoft clowns. This issue is just too easy to avoid. I'm sure I missed it in the documentation somewhere....
My original premise is that this was a VC6 application. Apparently, someone ported it years back to VS2015. So, not too old.
Anyway, MFC from the beginning (I'm going a long ways back, so I might be wrong), Microsoft's approach was to generate a stdafx.h and .cpp file that pulled in the MFC and Win32 definitions and what have you. If you were using something special for your application, you typically added it to stdafx.h.
Fast forward to sometime later (I don't know when MS decided to change the approach, I'd have to start downloading each VS to see how it behaved). Creating the dummy mfc app and staring at it for a while, I noticed there is no stdafx.* files. Instead, the newer versions of VS use a framework.h including a targetver.h - framework.h seems (I have a small test set admittedly) to be included in all of my application files. Within targetver.h, we include SDKDDKVer.h which is the magic file that fixes everything.
I would argue that the conversion report should include some sort of message about this.
Documented for posterity.
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
|
I do not have to compile or debug the code on Mac - only to run it.
Thanks
Nick Polyak
|
|
|
|
|
I'm somewhat confused. What is a 'remote MacOS desktops'.
Is setting up a virtual Mac too naive to solve this?
|
|
|
|
|
Virtual Mac would be great also. I just do not know how to do it or where to buy it. There are plenty of instructions for setting up a virtual Linux machine - which I did, but I could not find good instructions for Mac.
Nick Polyak
modified 15-Dec-21 14:39pm.
|
|
|
|
|
|
The problem is I want to get the BigSur.iso from a reliable place (e.g. apple) and apple does not seem to allow me to download it on windows.
Nick Polyak
|
|
|
|
|
If you private message me, I can give you some hints.
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
|
I do not see how I can private message you from the codeproject site, unfortunately. If you want connect to me on linkedin (I provide a link next to my profile) and there we'll be able to exchange the messages or you'll be able to see my e-mail address.
Nick Polyak
|
|
|
|
|
VM on non-Apple hardware?
Difficult, illegal, but not impossible. The Apple Eula disallows installing Mac OS on non-Apple hardware. There are sites that provide instructions though.
>64
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
|
|
|
|
|
|
It is very easy, but I want some solutions preferably tested by others. Perhaps this is not the best forum for Mac OS
Nick Polyak
|
|
|
|
|
I'm sending this from my Hackintosh. I think that's what they call it.
I don't feel bad, because I have a Mac-mini sitting on my desk. It works like a champ. I run it under VMWare Workstation Professional, but I know it runs elsewhere.
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
|
|
These bastards refuse to upgrade my dotnet runtime. I am looking for someone instead of them.
Nick Polyak
modified 16-Dec-21 12:01pm.
|
|
|
|
|
|
|
I have never come close to solving one, but this occurred to me while doing same:
Using precious metal to repair a failed Viking invasion (9).
I figure it is child's play for the resident experts.
>64
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
|
|
|
|
|
Maybe the CCCs seem inscrutable because you're unaware that they actually follow rules.
The first rule is that the beginning or end of the clue must be a definition for the answer, just as in a regular crossword. The answer to yours could therefore be utili*ing, with using being the definition, and the * being an s or z.
It must then be possible to use the rest of the clue to construct the answer, as described in Types of cryptic clues[^]. Precious metal might therefore be Au or Ag, a failed Viking invasion might be a battle site with 7 letters, and to repair might be an indicator that the Au or Ag must be inserted into that battle site to create the 9-letter answer.
|
|
|
|
|
Well said Greg
"Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP
|
|
|
|
|
I knew there was a reason for my stupidity.
Thank you, I will crawl back in my den never to CCC again.
>64
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
|
|
|
|
|
Noooo, don't do that. I'm not good at them either but they are quite fun.
Keep at it
// TODO: Insert something here Top ten reasons why I'm lazy
1.
|
|
|
|
|
Again, thank you. I should have added my feeble attempts answer.
Precious metal, silver. Repairing from a RAID (mirror) = Silvering. Just had to do that with a failed disk in TrueNAS.
Sorry.
>64
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
|
|
|
|
|
That is why I have two RAID5 NAS boxes under my desk: I had one HDD go down in the first one many years ago, and only noticed because a big red light started flashing on the front. Bought a new disk, slammed it in, and carried on - at no time did I lose any data or any access to my data (except when the box was unplugged to swap the physical disk).
Not so when it's your PC disk that starts to break ...
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Yup!
Had one that served us well for quite a few years but they didn't update the TLS version in firmware. I supposes that was to promote sales of the newer model. It didn't owe us anything but we moved on to our own box running TrueNAS. We have the box set up to send emails with status.
The one caveat about NAS boxes (off the shelf or DYI): it is not a backup system, it only covers you against hardware failures in your backup system. Had a client hit with ransomware but, because there were no systems with mapped drives to the NAS and the NAS blocked connections from all but one system, it didn't get compromised.
Back in time, they (whoever they is) recommended against RAID5 for large drives. Seems that during rebuild time, it took more operations than the failure rate of the drives. Haven't seen that recommendation in a long time.
There was a long rant on TrueNAS forums taking one of the disk manufacturers to task for using SMR vs CMR technology in their NAS drives. They now offer both.
You are not paranoid, they are out to get you.
Edit: oops, meant to say the RAID in the NAS.
>64
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
modified 16-Dec-21 5:56am.
|
|
|
|