Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


All Activity

This stream auto-updates     

  1. Past hour
  2. Although NVopenGL.dll works well KEX disabled it meeds BASE setting to stop VLC exiting error. BASE is the best setting as it does not impact frame rate noticeably. I have taken this theory to some other libraries that have no implicit load library errors but still needed NT setting. Examples include Activeds from DSclient for Win95; Libeay32 & SSLeay32 vs 1.0.2.4; dnsapi vs 5.1.2410.1. This idea should not be taken to all though as *\*.SCR should still be set to NT40 as if setting to BASE the ReactOS screen savers can throw the NVopenGL error on exiting even when NVopenGL is set to BASE :- it seems to be a timing issue IMO. Riched20 14.0.7155.5000 needs NT40 or better to perform properly not DCFG1 same goes with 5.50.99.2070, I chose Win2K_MT. I have User32 set to NT40. All seems to be having no ailments so far & bound to change some settings in future but getting KEX settings correct is not easy.
  3. Today
  4. Hi I have 3 rigs, one in work with 10 which I hate a lot (tried to purchase the ltsc version but is too expensive tho...), current with I7 that does not support win vista ( :/ ) and the other more new with ryzen 7 which I read in this forum a post with the full cpu support list for vista so I will try it. Only I do need know how integrate drivers. You are a guy with crazy luck with your old pc
  5. Gotcha. So NNN4NT5 is mandatory, but it's already enabled on my system. Interesting. By that, do you mean Administrator/Standard/Restricted? I found it interesting that W2K's "Restricted" is the equivalent of "Standard" in modern versions of Windows. Standard is not really around today, unless maybe that's power user or something. Yeah, I think we're really on the frontier, now. Don't get me wrong, Outlook 2007 on W2K is pretty nice, but Outlook 2010 would be really amazing. Although, right now, my first priority is getting encrypted documents to work correctly. Are you able to edit and save them, or do you also get errors of various kinds? Until then, Office is still only half-functional for me. How might I go about finding the problem? Also, here's a consistent bug I've noticed in Outlook: I double-click an unread message and read it. I close it and then when I double-click a second unread message, Outlook immediately crashes. If I double-click a read message, it doesn't crash, and I can keep going. A bit weird. Unfortunately, they show up in Event View but it's not really helpful: ID: 6, Application Name: Microsoft Office Outlook, Application Version: 12.0.6607.1000, Microsoft Office Version: 12.0.6612.1000. This session lasted 33 seconds with 0 seconds of active time. This session ended with a crash. ID: 6, Application Name: Microsoft Office Outlook, Application Version: 12.0.6607.1000, Microsoft Office Version: 12.0.6612.1000. This session lasted 1468 seconds with 540 seconds of active time. This session ended with a crash. I get something like that every time it crashes. Wait, there's actually useful crash information in the Application Log. Here we go: Faulting application outlook.exe, version 12.0.6607.1000, stamp 4e398dcd, faulting module version.dll, version 5.0.2195.7019, stamp 41de2adb, debug? 0, fault address 0x0000261d. Faulting application outlook.exe, version 12.0.6607.1000, stamp 4e398dcd, faulting module version.dll, version 5.0.2195.7019, stamp 41de2adb, debug? 0, fault address 0x0000261d. Faulting application outlook.exe, version 12.0.6607.1000, stamp 4e398dcd, faulting module version.dll, version 5.0.2195.7019, stamp 41de2adb, debug? 0, fault address 0x0000261d. Faulting application outlook.exe, version 12.0.6607.1000, stamp 4e398dcd, faulting module version.dll, version 5.0.2195.7019, stamp 41de2adb, debug? 0, fault address 0x0000261d. That was 4 different errors, I guess it's the same error causing a crash every time. At least this helps narrow it down! The crashes are not random, but due to one specific cause as indicated by the errors. Unfortunately, no useful information about the encryption errors, I just get: ID: 0, Application Name: Microsoft Office Word, Application Version: 12.0.6612.1000, Microsoft Office Version: 12.0.6612.1000. This session lasted 18 seconds with 0 seconds of active time. This session ended normally. The encryption is a bigger problem, and there's nothing in Event Viewer to narrow it down. Ditto for the error I get in Excel when doing the same thing. EDIT: The following also appeared, but I'm not sure from what: EventType offdiag12, P1 87967bb8-c803-4ab9-b47a-f5f36f6d49ca1e9bb9ec-e88d-48f3-b047-2f30cbdf06fa, P2 NIL, P3 NIL, P4 NIL, P5 NIL, P6 NIL, P7 NIL, P8 NIL, P9 NIL, P10 NIL. And now, something weird has happened where opening Outlook screws up the computer. Can't use it at all, I just get the five fingers mouse over, and if I open an Explorer window and drag it around, it copy cats itself all over the Outlook window each time I stop. If I kill Outlook, this goes away. This happens even after a reboot. Honestly, I'm more annoyed with the encryption errors than with Outlook. I suppose I could use Outlook just for calendars, and use another mail client that natively supports W2K until it's working more smoothly (suggestions?) @win32I wonder if the encryption errors are related to crypt32 or not. Unfortunately, I didn't think to try saving a document even when we had replaced crypt32. So I copied crypt33 to the desktop, renamed it crypt32, and then used replacer to replace the actual crypt32 with the crypt33 file. I know this will break Outlook, but I wanted to narrow down the encryption issues. I rebooted and now in Word, I get the make sure the disk is not full error when trying to save. Excel gives the same error as before. So, no dice. I guess regardless of whether Outlook works or not (which crypt32 is used), you can't edit encrypted files as it is. Thoughts on a solution?
  6. You are using an obsolete reg file. Here is the proper one: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\WPA\POSReady] "Installed" = dword: 00000001 There must be a single blank line after the first line. Use Windows to create the file, do not use Linux, it's just more headaches, testing, etc.. For instance, Gedit in Linux creates two blank lines instead of one. Here is more information about reg file format: https://support.microsoft.com/en-ca/help/310516/how-to-add-modify-or-delete-registry-subkeys-and-values-by-using-a-reg Btw, you can also use Clonezilla to create an image of a single partition. I have a few instances of XP, POSReady 2009 and Win7, some with .Net, some without, on a single computer (with two hard disks) and Clonezilla installed on its own dedicated Ext4 partition. Works like a charm.
  7. All videos play on your website - with JavaScript whitelisted (permitted) and in uMatrix permitted (green): all cnn.com and cnn.io, and pmd.cdn.turner.com. Twitter videos play here, but badly (very poor quality, in other browsers too). To play twitter videos, in uMatrix permitted all twitter.com and twimg.com, but I've these forbidden (=in red) in my uMatrix v1.0.0: analytics.twitter.com, syndication.twitter.com, cookie and other under twitter.com, image under abs.twimg.com. What do you think about?
  8. oops, a slash is missing in packing script. reuploaded.
  9. After more than one month without updating Serpent 52, I decided it was time to do so... and, after installing the latest binaries (basilisk52-g4.4.win32-git-20191207-2529b2ede-xpmod) I found out CNN.com's videos weren't playing anymore. Then I went to the previous version and so on, until I got to basilisk52-g4.4.win32-git-20191116-3492ad652-xpmod, which works as expected. I'm astonished: hasn't anyone reported any issues till now? I'm reporting an issue which prevents both videos at cnn.com (try: https://edition.cnn.com/2019/12/07/asia/beijing-pets-cat-dogs-intl-hnk/index.html) as well as most videos on twitter, and I found it out less than one hour ago!
  10. @Dylan Cruz The Outlook crypt32 error happens when it thinks it's running on anything else but XP. And the encryption issue seems to do with user privileges, which are handled differently in XP. That is the same issue that is preventing us from installing Office 2010 and VMware Workstation 10! The other way around would be to replace even more win2k native/BWC DLLs and run the risk of even greater breakage. I don't have that amount of time until I can get a few other commitments out of the way, which should take me a week. Because that does sound kinda fun!
  11. @win32 OK, so it was too good to be true, perhaps, and sure enough, I've uncovered a few bugs that have got me stumped again: It seems we only focused on half the puzzle. *Decryption* in Office is working. However, I'm unable to *edit* any encrypted files. When I try editing/saving a Word doc that is encrypted, it whines that it can't save because maybe the disk is full or write protected. This is even when saving to the desktop! In Excel, I get a different error: cannot access the file C:\Documents and Settings\Administrator\Local Settings\Temporary Internet Files\Content.MSO\3736C000. Makes no sense to me what temp. Internet files have to do with this. How do I know it's encrypted files only? So far, I've had no issues working with files that aren't encrypted. So it seems we're closer than before, but encrypted files are basically read-only at this point, for reasons that don't make sense at all.
  12. there are other junk sites like this one that claim XP compatibility, you only know if its XP capable once you donwload the software
  13. This appears to be an empty archive (32 bytes long).
  14. ... Unfortunately, this link currently only downloads a file sized a mere 32 bytes...
  15. @win32Bad news... things were working fine... now all of a sudden, I get the dread "CRYPT32 incompatible error" again... I haven't changed anything! It started with TCP/IP errors, nothing was connected, and when I logged into a new account, that's what I got. Somewhere along the way, things broke... I think time took it's toll, and maybe Windows internally did something weird as it was doing its usual Windows stuff. Does your Outlook still work? What if you try to add a second account? If I restore back to right when I did the restore, it works. But who knows where it went wrong. Somewhere, Outlook went willy nilly off the rails again. Once I restored, I could connect a Gmail and a Yandex account. I've spent some time working in Outlook 2007 now and changing settings. Not yet to the actual sending/receiving part yet. Conversation view, like in 2003, is pretty much broken/nonexistent, as that didn't come until 2010. Just out of curiosity, how hard would it to be to install Outlook 2010 *standalone* on W2K? I'm perfectly happy with the rest of the Office programs, and 2007 is a bit better than 2003, for sure, but I'd be interested to see if that would work/is even possible. Especially since XP supports both, so I'm not sure why KernelEx supports 2007 but not 2010. Also, in Outlook 2007, does the Calibri font work for you? Mine looks more like 2003 than the 2010 interface in terms of font. This was on XP, so it looks all nice: Whereas on Windows 2000, Outlook 2007 just looks so much more ancient. Is this possibly because W2K doesn't have the "round font edges" setting? **EDIT:** Fixed - go to Effects and click "Smooth edges of screen fonts". Everything looks *much* nicer now! Edit 3 hours later: I've been using Outlook 2007 quite a bit now and it's been mostly working so far. Several crashes, but not enough that it's unusable. It's not really any less stable than Outlook 2010 on Windows XP, and that was an officially supported configuration by Microsoft, so I'd say the outcome has been quite good so far.
  16. Well, when you put it THAT way... Point taken about ENDLOCAL. The matched quote routine was written to deal with other various variables, and was just reused for this application since it was handy, but your routine is MUCH more efficient when dealing specifically with paths. The errors aren't MY errors, but because of the data dealt with or user input. But like I said at the beginning, I'm sometimes guilty of the belt + suspenders approach to coding. Cheers and Regards
  17. Yesterday
  18. (Click Here) Dutch Boy and the Dike (story) Perhaps you have not enough fingers for Privacy Dike Plugging? Actually, no idea much here on 'IP Privacy' issues. Maybe a PAY ($$$) VPN Service would work for you? (Click Here) Project ECHELON Besides, they know about you anyway!
  19. @Dylan Cruz That happens to me too. Probably because it expects a different XP-style UI rendering routine, but can't confirm.
  20. OK, found it and install, looks like it worked! I didn't realize the roots update files were continually being released. I applied the roots update from 2017 and that allowed my Chromium 54 to work with HTTPS once I rebooted. I didn't need to reboot for Outlook to stop warning me, though. Interesting. Complete guide should now be fully up to date: https://w2k.phreaknet.org/guide/ I don't think anything has been left out. Just out of curiosity, when you go to Tools -> Account Settings, what do you see? I don't see my mail account listed there. I haven't, this whole time we've been testing. I thought it was something weird, but I think it's more like the Office activation think where I had to replaced riched20 dll for that to work right. You can see that something is highlighted, but there's no text. If you click Change, then the email account settings come up. Not a big issue, since there's no need to access this on a day to day basis, but I can imagine it might be confusing once I put 10 accounts in here and they all show up as invisible!
  21. @Dylan Cruz Click "Manual Update" on the left sidebar, then several English search fields will come up.
  22. Uh, what do I click, exactly? It's all in Japanese. Usually, there's a translate option, but not this time, and there's no English really.
  23. Yes thanks for your detailled response, TechnoRelic! foxyproxy in BNAV ... so why, on BNAV, IP check websites show my true IP, please? WHOER extended: https://whoer.net/#extended JonDonym: http://ip-check.info/?lang=en Aaron Horler: https://aaronhorler.com/ ... and Roytam1: https://o.rths.ml/test/ip.php Have you an proxy/vpn extension working on other RoyTam1's browsers, please? If not, test "legacy" Zenmate extension et get your impressions here, please... Link to download Zenmate: https://web.archive.org/web/20191029181657/https://legacycollector.org/firefox-addons/541038/index.html ... or download "legacy" Browsec, if you wish: https://web.archive.org/web/20191029180612/https://legacycollector.org/firefox-addons/603434/index.html Thank you!
  24. @Dylan Cruz Install the latest root certificate update (July 2019) from blackwingcat's Windows Legacy Update (http://www.w2k.flxsrv.org/wlu/wluen.htm) I did find consistency to the crashes; they happen when attempting to open an unread email for me. I marked them all as read and the crashes stopped.
  25. A bit late, but you can obtain the XP/Vista version here: https://getonline.aol.com//xp-vista It's now version 1.0.0.35
  26. Did all this, when I test my settings, I get the The server you are connected to is using a security certificate that cannot be verified... A certificate chain processed correctly, but terminated in a root certificate which is not trusted by the trust provider. Do you want to continue using this server? I click Yes twice and the tests pass. Next->Finish. And then my mailbox loads!!!! Yes, it works!!! I'll have to test more of Outlook's nuances, but I will update the guide. I guess we can have our cake and eat it, too! Thanks again @win32 - really looking forward to using W2K as my primary OS now. UPDATE: In the time it took me to write this response, I went back to Outlook and it had crashed. Ah, I supposed that's to be expected, though. I do get the certificate error every time I open Outlook 2007. A very similar error happened every time I opened Outlook 2003 on vanilla W2K, but that happened twice for every single account. This happens only once, though I only have one account connected at this time. Any way to permanently disable the warning? If not, it's not the end of the world - as long as it doesn't do it once per account/server. UPDATE 2: I relaunched Outlook and tried to open an email, and then it crashed again. But I did it again and it didn't crash, so I guess it's not consistent.
  27. Wow, I'm an id***. I looked in Program Files\Office12, not Common Files\Microsoft Shared\OFFICE12...
  1. Load more activity
×
×
  • Create New...