Kpsa4
Content Type
Profiles
Forums
Events
Posts posted by Kpsa4
-
-
@xYannikx Where exactly does this screenshot come from? I can see there date 9th Nov 2024. That is not much old, but if the original vxiiduu is still somewhere around online, why he doesn't simply do some official statement to all those speculations? No offense to you at all. I'm glad people here post any info they have. But anybody can create such a screenshot, anybody can use vxiiduu nick on some instant messenger. It might me real, but also maybe not. I don't know. If you have more detailed info, post it please.
@D.Draker Who knows if that story is real or not. Maybe just somebody wanted to fake it, because VxKex really needs to be updated, so we can run new versions of software on Win7. There is for sure more people who got skills and time for that, but nobody wanted to start, if the status of original project has been unknown. Now at least 2 people started to do some work on it and that is imho good at this point. Future will tell more.
2 -
Well if you are talking about Github and the laws. One thing is what they declare and the second thing is the reality and what they really force and remove. I will not post the links as it is not allowed here, but there is multiple software hosted on Github allowing to bypass the protections and the licenses of various commercial software and allowing the people steal it. And it’s there hosted for ages. Like 7 years for example and that was of course before the new Russian law and looks like nobody cares at all. That’s imho little bit strange and I got a feeling from that, they don’t have the same meter for MS and/or other big companies stuff and the rest.
2 -
19 minutes ago, D.Draker said:
No, on the contrary, your English is good. I wish many others had at least your level. Today, I wanted to stick forks in my eyes when I saw "maded" written by a dude who claims to be a "developer", lol.
So, I just made you a compliment, as you see, I'm not here "against you", either. What I wanted to tell, we know that Kernel developer from here, he is a member, I don't trust github either, I trust MSFN.
Edit.
Nothing personal, it's just we had some MSFN haters joined as of lately. So some folks may be a bit agitated and over-protective.
All fine. Also nothing personal from my side. As you can see I'm not much active here. I'm here for 2 years with just few posts and half of them in last days in this topic. That's why I don't know about the haters. I also know that the original vxkex developer got account here, but looks like he was not much active here recently. But with my reply I just wanted to make it clean, that the first "fake" post was made by me, but there is easy way to verify it is not somehow tampered at least in this case if it's also on web archive. And even that fake one deleted now got the binaries binary the same as the original. You can still verify that on web archive here:
https://web.archive.org/web/20240723221328/https://github.com/VxKex/VxKex/releasesBut I fully agree with you, that everybody needs to be cautious when installing anything from internet and specially if it's new or unknown source and the target software got high level of system access.
1 -
41 minutes ago, D.Draker said:
Good! Thanks for coming out with the confession, then the supervisor will keep an eye on you, too.
No problem. Feel free to keep an eye on me here. I don't care and as you can see I have nothing to hide here and that's why I made this "confession".
QuoteNo one is "paranoid", we are just being on the safe side. I mean, do you realise how serious is to install kernel from unknown, non-developer sources!?
MSFN only hosts and provides 100% clean originals. The same with external links. We can't just take someone's word for it, sorry.
Might be language barrier, as I'm not native English speaker, but by "it is good to be paranoid" I actually mean it is good you don't trust any random person on internet. I'm not here against you. And of course I know it's serious to install kernel or any similar software from unknown source. But basically anything might be infected. Even "known" source. What is known anyway? There are tons of software on Github and tons of various forks. Not everything is clean. You always need to use common sense. And you can check the sources if you have the skill or debug it. But it this case only what you need to do is compare the hashes or compare the files binary by content. I'm sure many people got the local archived version from the previous source to do it. And if they don't have it, there is archive.org. And there is no way to provide original source if the source has been deleted included the original account. If we cannot discuss here such new external links. I see no point of this topic at all as the original developer might inform us in the original topic about VxKex if he wants.
43 minutes ago, Dixel said:Compare with what? What if the user is new, and doesn't have any of these from before? Since the original repo is gone, as you wrote yourself.
Compare with archive.org versions if you don't have your own copy and of course they are available. here:
https://web.archive.org/web/20240712131314/https://github.com/vxiiduu/VxKex/releases38 minutes ago, Dixel said:It doesn't let me to download.
The download from there works just fine for me. Must be problem on your side or in your browser, but I don't know why are you trying to download i486 archived version and not the original vxiiduu version from the archived link I provided above.
0 -
Guys, it is good to be paranoid, but there is nothing fake on the commandcontrolQ one. If you check that Github page there is clearly written:
This is an archive of the VxKex repository from the user 'vxiiduu', whose account was deleted on the 21st of July 2024 for reasons currently unknown. I am not planning on maintaining VxKex any time soon, so I will be disabling the Issues page.So somebody just reuploaded and clearly written its just reupload from the original account. What is fake about it? And you can always compare hashes with your local archived version or archive.org version if they are available to be sure its not somehow tampered.
And it was actually me who posted the other fake one, but I have clearly written it is just info from that ycombinator.com website. And then I also posted its marked as fake on the i486 repo.
But according your logic the i486 one where was written the second one is fake is fake as well, because the i486 user is just somebody who was very active in the previous original repo, but not the original owner.
Imho nobody in this topic wanted to post here any fake or harmful info, but as @vxiiduu didn't make any official statement here, we can just speculate what happened.
0 -
The VxKex/VxKex now also removed. Here is another one and according to the description there the VxKex/VxKex was fake one. Too much mess around it unfortunately.
0 -
On 7/20/2024 at 9:52 AM, lll888 said:
Previously, after recovery, my computer worked for a maximum of 20 days, after which it began to become very slow and I had to reinstall win, so I abandoned the recovery completely
It probably means you are doing something wrong with your computer or there was some specific rare issue. Disabling system restore is bad idea in most cases, but there might be of course some specific usage exception. Reinstalling the system is faster only for people who don't use many specific custom settings and many specific software with many specific custom settings, system drive encryption etc etc. The system I'm writing from now has been installed 9 years ago and it still works perfectly. During that time I've used system restore maybe 2-3x for example when there was problem with some new driver and system failure to boot. During that time I also fully replaced the hardware and migrated the OS from old PC to new one by cloning the encrypted system drive. It needed some fixes, drivers reinstall etc, but it was still done in maybe 2 days. If I need to reinstall the whole system from scratch and reinstall all the software and settings I have here, I need at least 2 weeks for that. But of course for people who use mostly default settings and few application the reinstall would be faster.
1 -
-
On 3/21/2023 at 2:24 PM, yoltboy01 said:
Off-Topic: It works with 8.1
On Win 7 I'm getting this:
The procedure entry point MFCreateDXGIDeviceManager could not be located in the dynamic link library MFPlat.dll.It seems to be Windows 8+ feature, so if it's only this, then it might still work on 8 as well.
https://learn.microsoft.com/en-us/windows/win32/api/mfapi/nf-mfapi-mfcreatedxgidevicemanager
Question is now how to fix this on Win 7.
edit: according to this is that function available on Win7, but in another dll https://stackoverflow.com/questions/26336450/solve-issue-unresolved-external-symbol-mfcreatedxgidevicemanagerv
MFCreateDXGIDeviceManager is in MshtmlMedia.dll on Windows 7, and in the MFPlat.dll on Windows 8 and higher.edit2: I've tried to install Win8.1 ISO downloaded from MS website inside virtual machine and I can confirm there it works after fresh installation. I've been trying to use some of the dlls from 8.1 in application folder on Win7, but best I can do for now is get rid of all missing entry points if I also enable VxKex, but the application just exit and don't run.
edit3: After editing ZCB.exe, Zps.exe and ZVFS.exe for both 32 and 64bit in CFF Explorer and replacing MFCreateDXGIDeviceManager with MFStartup program seems to be working again fine on Win7.
edit4: Method of patching mentioned above will make some video preview features not working, but if you are using Zoner Photo Studio only for photos and don't need video features much, you should be fine with this method as temporary solution to use updated version on Win7, before there will be be better solution.
0 -
Zoner Photo Studio X drops 7/8/8.1 support with 2023 spring update. It doesn't run with VxKex on 7 as well.
https://www.zoner.com/en/zps-x-spring-2023-update
We are ending support for Windows 7, 8, and 8.1, as well as all 32-bit operating systems.1 -
16 hours ago, Darth Agnon said:
From my notes (untested):
Any chance you could test and let us know if this workaround works?
There are already multiple versions compiled with QT5 and fully working on Win7.
First one you can grab here: https://forum.videohelp.com/threads/405407-NON-OFFICIAL-Windows-builds-of-MKVtoolnix/page3#post2672418
Second one here: https://github.com/jpsdr/MKVToolnix-QT5-Windows-7
The first version seems to be updated regularly and available few hours or days after official release. It is opensource, so everybody can do this.
2 -
On 7/14/2022 at 8:42 AM, ED_Sln said:
Mkvtoolnix 69 does not work in Win 7 and 8.1. The developers have added a lot of new system calls and libraries like api-ms..., which are not present in either 7 or 8.1. VxKex also did not help, there is no system call in user33.dll, so I couldn't run it in any way mkvtoolnix-gui.exe.
mkvmerge.exe starts after adding api-ms-win-core-synch-l1-2-0.dll, so that anyone who uses the console version can continue to use it.
First unofficial build with QT5 for Win7/8.1 is here: https://forum.videohelp.com/threads/405407-NON-OFFICIAL-Windows-builds-of-MKVtoolnix-do-they-exist#post2663774
1 -
On 7/17/2022 at 1:07 PM, ED_Sln said:
It doesn't work, there are no errors, it just doesn't start. VxKex didn't help either.
I've been able to run Calibre 6.1 on Windows 7 x64 using this method:
1. Download Calibre msi file from homepage and patch the installator using Orca to be able to install it on Win7
2. Copy and replace these QT6 Win7 compatible files from here: https://forum.qt.io/topic/133002/qt-creator-6-0-1-and-qt-6-2-2-running-on-windows-7
https://web.tresorit.com/l/iWnTl#yGMg45iqZObF8miEZt7FaA
3. Use VxKex to run Calibre
1
VxKex (extended kernel) project dissapeared
in Windows 7
Posted
All fine and I understand what do you mean with the verified MSFN account. But this is only your point of view and maybe point of view of some other people here, because you and them are active here for some time and know this place and trust it. But let’s start thinking about the global reality. And the global reality is most of the people probably don’t even know MSFN forums exists. Some of them don’t even prefer to use Github as it should be used. The example is the Chinese guy here:
https://github.com/i486/VxKex/issues/36#issuecomment-2508751433
But it doesn’t mean he wants to make trouble for anybody. I fully agree with you, that system kernel extension is very important part of the system and if somebody wants to make bad things, this is really good opportunity. But on the other side Win7 is no more something masses are using. Those , who are still using Win7, usually got reasons for that and that means there is more percentage of users with some higher level skills, included debugging. They can check and inspect the final product..
Also look what MS did with newer versions of Windows. Tons of crap added, tons of telemetry etc. Where is the trust anymore? That is for example one of the reasons I’m still using Win7 and I don’t plan to switch to more recent versions of Windows at all. I’m using Linux distros on server machines, but on desktop I still prefer Win7 and I hope it should be good at least for few more years.
In my opinion if the Win7 extended kernel project might be working and live project for the future, then we need everybody who got skills and time to work on it. Such a project cannot be single man project in long time period. And as far as it is kept open source, there is imho enough ways to control the possible bad attempts.
I also think that all those rumors and saying this is “fake” - this is not “fake” might be something what keeps some people away from the project, because they simply don’t want such a bul***** in their lives.
MS did with newer versions of Windows what they did. It is no more what it was before. And there are people who never accept the new Windows concept and if those people want keep using last non-crippled Windows version – Windows 7, then those people must trust each other and cooperate together. We are these people. That’s the only way we can keep Win7 alive for new versions of applications and continue to use it.