Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 01/31/2019 in all areas

  1. Have new build generated by ProxHTTPSProxy v1.5 (Rev3a), with small changes script, various python modules updated, config.ini supplemented by some entries, CA certificates (cacert.pem) updated and alternativ cacert.pem from MSCerts (Cert_Updater) 11/28/2018. If anyone has interest please write a PM to me. Info: At Python 3.44 the support ends in March 2019. With the latest cryptography module version 2.5 (Jan 22, 2019) ProxHTTPSProxy does not work on Windows XP anymore. Last working version 2.4.2 (Nov 21, 2018).
    3 points
  2. Don't know why they don't work for you, but I can confirm they work fine on my end.
    1 point
  3. Sure it is! Alive and kicking fiercely!
    1 point
  4. Recently I've tried to port Windows Meeting Space over to Windows 7, but it's not working. I've gotten interested in the program since I like how it's free, p2p, has a bunch of features and stuff to go with messaging, and doesn't have a file sharing size limit (at least im pretty sure, ngl i haven't gotten to use it too much but if it's anything like NetMeeting, count me in). I just thought it'd be cool if I could run it on my 7 partition and maybe give it to some of my friends so we could get past the "le epic gamer" Discord with it's pitiful 8 MB file sharing size and crappy snapchat-ripoff Skype. So basically, to make a long story short, I copied over the x86 & x64 Program Files for it ("Windows Collaboration"), got the p2pcollab.dll stuff from sys32 and sysWOW, as well as went through the program with Dependency Walker and Process Monitor to basically hack together a bunch of needed dlls from my PC and stuff... But: nothing. Every time I open the program it just immediately closes. Not crashes - just closes. Then I realized that it's probably not so much an issue with dlls and things (since a newer version of Windows would obviously have everything that Vista has), but probably more along the lines of Windows product activation or something. So I guess this post is more of a plea - how the hell do people hack programs like these to make them work on newer versions of Windows? I mean, people have already ported over all the games from Vista/7 to 8/10, so it's not like it's impossible, but there really doesn't seem to be ANY starting point/tutorial anywhere to do something like that - at least, not open in the public. Something's telling me there's probably a reason for that though - and I'm sure the solution probably has something to do with some complicated hex editing or etc. It's not the end of the world if this never gets resolved, but I just think it'd be really cool to have this program on 7/10. If anybody can help, say somethin.
    1 point
  5. Thanks for providing an alternative, it looks like it should work well enough for me. I don't know how I never found this earlier. I tried doing a profile of WinCollab.exe on both 7 and Vista. I personally couldn't find any errors that really stood out to me, so I'm kind of stuck now - on 7 it references dlls like "KERNEL32.DLL" and "KERNELBASE.DLL" that Vista doesn't even use at all, and it just seems to end kinda peacefully without some major error I can identify. I did notice that Meeting Space has some sort of tie to the "People Near Me" (p2phost.exe) program, so that could add an entirely different layer to the situation. All in all I think the issue is with the program, not its dependencies - there's probably something in its code that checks for a specific product key or version of Windows, and I don't know how to change any of that, so I might just step down for now if that's the case. All the stuff about porting on the 2000/9x forums seems more tailored to those specific operating systems and dlls and stuff as well, so I wasn't able to find any help there (maybe I didn't dig hard enough?). I'm going to provide the profiles I did on WinCollab on 7, Vista, and the P2PHOST thing that DW switched to after WC on Vista. If anybody wants to take it from here or give some advice, go ahead. (I think I might've messed up the settings on one of the profiles, so if you need me to redo them I can.) WinCollabProfiles.zip
    1 point
  6. Edit 29 May 2015 - add green text I think I figured out what's going on, at least for my own system since I've gotten rid of those eventlog entries. And it seems just KB3021674 is the immediate culprit since the KB mentions that one "could leverage the Windows User Profile Service (ProfSvc) to load registry hives that are associated with other user accounts". I think the Local Service and Network Service used to do exactly this to borrow access they should not have had, possibly from SYSTEM, which is why it used to work for me before the update but afterward didn't and actually never should have, given some of my file permission settings. The good news is that the update does not need to be uninstalled to solve it. The first clue is in a thread about this update going wrong for Vista/W7 users, but the basic outline is the same for XP and/or WEPOS 2009 as well even though nobody mentions it... see the third post by Susan Bradley on http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_update/kb3021674-causes-user-profile-event-1542/f203ebf9-08f5-4b95-84af-fbe8c52f3854?page=3 To dencorso and glnz, could you both check what account is the owner of the folders: C:\Documents and Settings\Default User C:\Documents and Settings\Local Service C:\Documents and Settings\Network Service C:\Documents and Settings\ (your account name) Mine are all owned by the "Administators" group, I'm thinking that glnz may have this too but perhaps dencorso does not? Also could you both open a cmd prompt and type cd c:\Documents and Settings cacls "Default User" > perms.txt cacls LocalService >> perms.txt cacls NetworkService >> perms.txt cacls (your account name) >> perms.txt then paste the contents of perms.txt here? In my case these showed that neither Local Service nor Network Service had any access to their own profiles since they were not the owner. The way I see it, the ideal solution would be to change the owner from Administrators group to Local Service and Network Service but the UI does not give me any way to do that... it can TAKE ownership but not give it away, and having it owned by either me or Administrator would not solve the problem. The other interesting post is on page 4 of that thread, in the Susan Bradley reply near the bottom, with the screen shots. But instead of focussing on "anyUser" as she does, check out NT AUTHORITY\Local Service and NT AUTHORITY\Network Service - giving them Full Control solved it for me. Also I had to do this for the entire folder (I also propagated to all children while I was at it), not just the files ntuser.dat and usrclass.dat - doing just those 2 files replaced the 6 errors with a pair of eventID1500's but didn't completely solve it. And yes, the mystery profiles for Temp and TEMP.NT AUTHORITY went away on their own after a reboot once I fixed all the permisssions, I did not need to manually delete the temporary profiles. If you have XP Pro you could follow the screenshots but for Home you would have to either reboot to safemode (so the normally missing security tab can appear on the property sheet), or (to view the current settings) use the command line to enter cd c:\Documents and Settings cacls LocalService "NT AUTHORITY\LOCAL SERVICE" cacls NetworkService "NT AUTHORITY\NETWORK SERVICE" or to actually do the fix: cd c:\Documents and Settings cacls LocalService /t /e /g "NT AUTHORITY\LOCAL SERVICE":F cacls NetworkService /t /e /g "NT AUTHORITY\NETWORK SERVICE":F then for either way, version of the fix, reboot. This worked for me.
    1 point
×
×
  • Create New...