Plaintive
| pronouns | she/her |
| main project | https://mermaid.industries |
| on bsky | https://bsky.app/profile/dryad.technology |
| avatar by | Dana |
@mcc
- 39.2K Followers
- 616 Following
- 87.6K Posts
glitch girl
Alright. Here is a request. If you, reading this, just happen to be on a Windows 10 or Windows 11 machine. Could you download this and run artist_windows.bat and tell me if it boots or fails to boot. IF it works, you should see this.
https://data.runhello.com/j/artist/3/ARTIST.zip
If it crashes or otherwise fails, please tell me what version of Windows (10 or 11) you are running. If it works, you don't need to tell me. It works on my machine. I'm trying to discover machines it doesn't work on (if any remain)
"Google is completely cooked" update: I looked in my spam folder and discovered that GMail is sending *its own delivery failure notification emails* to spam. The sender is "googlemail.com" and is cryptographically signed, and receiving this email is critical for regular use of GMail. Went to spam
Back on Linux where things work, I'm looking at the invisible FOUND directory and its many CHK files. There are 1,364 files which roughly fits the number of files that one day mysteriously disappeared (possibly because CHKDSK fucking deleted them). The file data is of little help to me but what would be super helpful is knowing *which files* disappeared. Does chkdsk store *any* information about the paths of files when it drops them in here. Or is the whole point it doesn't know
Update
I haven't figured out if any content is lost, but I think I now regret running chkdsk.
Oh, also
* The disk is STILL marked dirty;
* There actually is no FOUND.001 directory.
Getting increasingly worried. It's still running and is up to claiming it's found something like 120,000 corrupt files in \FOUND.001\. Some files did disappear from this disk at some point, but not this many. I am now terrified chkdsk is in fact not *checking* the FOUND.001 directory but is *moving* the corrupt files, in other words, it is deleting every single file on the disk by copying it to FOUND.001 at which point I will never reconstruct the directory structure
It's currently spending many many minutes printing hundreds of lines of this. Oh?? You found corrupt files in the directory where you keep the corrupt files?! Is that so !?!
I'm editing a Visual Studio (not Code) solution. I believe I need to add to "Additional Library Directories":
$(SolutionDir)\..\..\bin\Windows\$(XXX)
Where XXX is some project property which is equal to "x86" on x86 builds and "x64" on x64 builds.
1. Where can I find the documentation that lists builtin project properties? I find
But it doesn't include $(SolutionDir) which appears to exist.
2. How do I get MSVS to show "verbose" builds that show EG cl invocations?
