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. 


TechnoRelic

Member
  • Content Count

    89
  • Donations

    $0.00 
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by TechnoRelic

  1. @roytam1 -- @Mathwiz -- @VistaLover <-- https://www.techradar.com/news/the-best-cloud-storage#best-free-cloud-storage Best cloud storage of 2019 online: free, paid and business options ... By Nate Drake 2019-10-08 So, the above article did list these FREE STORAGE option services --> Google Drive -- pCloud -- MS OneDrive -- Dropbox -- MediaFire I have no idea which of these (if any) might serve as a Storage Solution for RT in some manner. I was thinking that they might serve as some kind of backup solution for RT, if nothing else. I have no idea what RT's BANDWIDTH demands might be. Just throwing this 'out there' so to speak. I was looking at "pCloud" where it said --> The only caveat to these plans is that limits are placed on the amount of traffic, so you can’t have a 2TB facility, but upload a different 2TB every day. You are limited to the whole amount in traffic per month, although remote traffic with files you’ve shared isn’t included in this cap. <-- Which, I interpreted this "although remote traffic with files you've shared ISN'T included in this CAP" to mean, that remote users (like me say) can download files (from RT via pCloud) as much as they want to do that ??? Anyway, posting this as a reference source for possible RT Storage Solutions. Added Later: Some Messages below have other ideas, which is all good as I see it.
  2. The newly released SeaMonkey 2.49.5 Browser supports WinXP (32bit Only) and Language Packs. http://www.seamonkey-project.org/releases/#langpacks And (MSFN User) 'VistaLover' created a FIX for INSTAGRAM Video for it under WinXP too. I like to support RT's Browsers though. I gladly use the RT BNAV Browser, but it has NO LANGUAGE PACKS available for it (so English Only). Sadly, LANGUAGE PACKS is becoming an 'issue' increasingly. https://msfn.org/board/topic/177125-my-build-of-new-moon-temp-name-aka-pale-moon-fork-targetting-xp/page/184/?tab=comments#comment-1170340 'VistaLover' FIX for SM 2.49.5 Browser -- For INSTAGRAM Video under WinXP OS (32bit Only). Note: Updated with '(32bit Only)' on WinXP OS situation per 'VistaLover' Message below. URL for RT BNAV Browser (English Only | Light Weight and Stripped Down 'SeaMonkey-esque' --> https://o.rths.cf/boc-uxp/
  3. That 'MAT' person strikes AGAIN !!! ... It is good that 'Mathwiz' did those 'HELP MENU' PULLS to 'Re-Aim' the related URLs for RT's Browsers.
  4. @roytam1 <-- Version: 0.9.0a1 (32-bit) Build identifier: 20190920 User-agent: Mozilla/5.0 (Windows NT 5.1; rv:60.9) Gecko/20100101 Goanna/4.4 Firefox/60.9 Borealis/0.9.0a1 With RT BNAV Browser, latest version = 2019.09.20 (see above). ALL of the EXTENSIONS and THEMES got DISABLED It says on ALL of them like this --> --- User Agent Switcher 0.7.3.1 is incompatible with Browser 0.9.0a1 User Agent Switcher 0.7.3.1 (disabled) --- I used this below (now incorrect) for fixing the INSTALL.RDF file for all my EXTENSIONS --> <!-- RT BNAV Borealis Navigator --> <em:targetApplication> <Description> <em:id>{a3210b97-8e8a-4737-9aa0-aa0e607640b9}</em:id> <em:minVersion>1.0.0a1</em:minVersion> <em:maxVersion>*</em:maxVersion> </Description> </em:targetApplication> Maybe this situation has to do with '1.0.0a1' vs '0.9.0a1' ??? So, listening here on possible solutions. (Added after reading 'VistaLover' REPLY Message Solution) --> Use 7-ZIP software to EDIT the INSTALL.RDF file inside of *.XPI Legacy EXTENSION files. (1) *Right* Click on the *.XPI file, and choose OPEN ARCHIVE (Top Most Menu choice) (2) Find INSTALL.RDF file listed, and *Right* Click it, and choose EDIT (Menu) (3) Find this (inside) for BNAV ... <em:minVersion>1.0.0a1</em:minVersion> (4) Change it to ... <em:minVersion>0.1.0a1</em:minVersion> (5) SAVE (EDIT), then CLOSE, get 'Update Archive?' and do that (SAVE, Yes) again. (6) CLOSE 7-ZIP, and the *.XPI file is ready to reinstall it via (Browser Menu) TOOLS, ADD-ONs. That should get the Legacy EXTENSIONS and THEMES working again in RT BNAV Browser. Here, I like the "Metal Lion Sea Monkey 2.0.4.5" THEME -- the ML *Silver* THEME is good too. Note: I corrected ALL my old Messages related to FIXING the INSTALL.RDF file related to making it possible to install Legacy EXTENSIONS into the RT BNAV Browser -- URL for BNAV is here --> https://o.rths.cf/boc-uxp/
  5. I am "content" now ... ... (Next is Intended as humor) ... And let me add that --> No GOOD DEED goes UNPUNISHED (or with no criticism) ... Seriously, THANKS again for your SM 2.49.5 Browser INSTAGRAM Video TWEAK (WinXP OS). I am certain that you have now helped MANY WinXP OS users who will NOT ever say 'thanks' to you.
  6. https://msfn.org/board/topic/177125-my-build-of-new-moon-temp-name-aka-pale-moon-fork-targetting-xp/?do=findComment&comment=1170340 @VistaLover <-- My suggestion, is that you should UPDATE your URL (above) with this added information: (1) media.gmp-provider.enabled;true (boolean) Place this in the LIST that you already have it there. (2) Include the ('sdfox7') Archive Download URLs for 'Adobe PrimeTime CDM' Plugin: (a) http://sdfox7.com/xp/sp3/EOL/primetime_gmp_win_x86_gmc_40673.zip (b) https://web.archive.org/web/20170718145441/http://sdfox7.com/xp/sp3/EOL/primetime_gmp_win_x86_gmc_40673.zip That way, EVERYTHING needed to install your INSTAGRAM Video Tweak (SeaMonkey 2.49.5 Browser) would be there in your one single message. So, a suggestion, do as YOU choose. And your solution (listed above) did successfully FIX it so that 'Adobe Primetime CDM' Plugin DOES now LIST for me under ADD-ONs (Plugins) for SM 2.49.5 Browser. I did set to OFF for the AutoUpdate of it. Hopefully, you ('VL') did NOT 'use up' a great deal of your time with 'scoping out' this INSTAGRAM Video Tweak. Anyway, count me as IMPRESSED, and THANKS again!
  7. I am replying so that you are not ignored. The situation is that the (BK55) ST55 Browser has a 'higher quality' JAVASCRIPT engine in it. So, as in the '55' number is greater than the '52' number. Having said that, RT only updates RARELY the ST55 Browser. The RT 'bread and butter' Browsers are NM28 and ST52 Browsers. Because they work well enough with a LOT of 'Older Age' CPUs that inhabit certain 'Older Age' Computer Hardware. RT has decided that the ST55 Browser is NOT so much a priority for him. Even though a LOT of USERS of RT's Browsers, have stated that ST55 works BETTER for them than ST52 does (myself included). But this situation on ST55 vs ST52, is RT's decision. And I just figure that RT is doing what HE thinks is BEST with his limited TIME and EFFORT. Maybe this makes the situation somewhat more clear -- maybe not. --- (Added Later Below) ... https://msfn.org/board/topic/177125-my-build-of-new-moon-temp-name-aka-pale-moon-fork-targetting-xp/?do=findComment&comment=1170437 'Mathwiz' did REPLY to your issue too. And his answer is better than mine. So, click this URL above.
  8. @Mathwiz in a recent previous message, observed --> "At this very moment, I like SM better (than RT's BNAV), but version 2.49 is at EOL; according to the SeaMonkey Project web site, there will be no 2.49.6. (Unless of course @roytam1 picks it up ). And newer versions won't run on XP." <-- YES, I was thinking the same about the notion of RT 'taking over' the SM 2.49.5 WinXP compatible Browser and Emailer in a 'FORK' situation. This might be a BETTER use of RT's TIME. In that, SM 2.49.5 Browser does currently support LANGUAGE PACKS installation. Whereas RT's BNAV Browser is ENGLISH Language ONLY at this point. As you pointed out, BNAV Browser is VERY 'Light Weight' and works WELL here for me and my OLD LAPTOP hardware and WinXP OS. But BNAV Browser is also LIMITED on EXTENSIONS supported, and some other 'features' that SM 2.49.5 Browser has that support better. And here, SM 2.49.5 Browser works rather WELL overall too. NOW that SM 2.49.5 Browser has the INSTAGRAM Video problem solved (via the 'VL' Tweak), I plan on using it MORE here. But I like the BNAV Browser as the most responsive one for me and my 'Hardware/WinXP' situation. Yet, IF that RT was to 'switch support' away from BNAV Browser, and move that to SM 2.49.5 Browser, I personally would SUPPORT that. Because of the LANGUAGE PACKS situation. With SM 2.49.5 Browser as a 'RT FORK' -- RT would be able to 'reach/help' a LOT more WinXP users on a GLOBAL basis. As opposed to the 'ENGLISH Language ONLY' audience that BNAV Browser has it. ------------ RT did REPLY in a Message below, and said --> "Maybe a 'one-shot' build (SM 2.49.5 Browser) can be done ... But please don't hold your breath for it." <-- My reaction is, that what RT decides to do it, is the BEST that can be done with HIS TIME and EFFORT.
  9. https://o.rths.cf/boc-uxp/ BNAV Browser Download (RT) RT has uploaded (URL above) this Extension file (xpi) --> foxyproxy@eric.h.jung.xpi FoxyProxy Standard 4.6.5 Extension NOT sure if or how that this relates exactly to your "PROXY" comments about BNAV Browser. But this Extension does install successfully into BNAV Browser and seems to function okay.
  10. https://msfn.org/board/topic/177125-my-build-of-new-moon-temp-name-aka-pale-moon-fork-targetting-xp/?do=findComment&comment=1170340 @VistaLover (above URL) did SOLVE the SM 2.49.5 Browser situation for INSTAGRAM Video (embedded) playback. Okay, SUCCESS here on using your ('VL') instructions for INSTAGRAM Video (embedded) playback with SeaMonkey 2.49.5 Browser under WinXP OS. But ODDLY here, the 'Adobe Primetime CDM' does NOT LIST under (ADD-ONs) the PLUGINS listing. However, INSTAGRAM Video playback seems FINE now for me, so PLEASED on this. THANKS to work out this solution. --- As added feedback (below) --- (1) Should make CLEAR that these are 'about:config' (address bar) entry changes. (2) media.eme.enabled;true (boolean) Did 'instant' create with 'FALSE' value (here). So, I changed it to 'TRUE' value (via TOGGLE). (3) media.gmp.decoder.enabled;true (boolean) Did 'instant' create with 'TRUE' value (here). So, no change needed. (4) Sourced from @mixit ; who provided earlier solutions to this INSTAGRAM Video (embedded) playback situation. 'MIXIT' said "Adobe has removed the (PRIMETIME CDM) package from download, but @sdfox7 has kindly archived a copy (along with a backup link)" --> (a) http://sdfox7.com/xp/sp3/EOL/primetime_gmp_win_x86_gmc_40673.zip (b) https://web.archive.org/web/20170718145441/http://sdfox7.com/xp/sp3/EOL/primetime_gmp_win_x86_gmc_40673.zip --- As added feedback (above) --- The ('VL') instructions are COMPLETELY CLEAR overall. No problem here to make the changes. This seems NOT a difficult 'Tweak' to make it happen, in my view. What this means, is that the SM 2.49.5 Browser can now support INSTAGRAM Video (embedded) and also LANGUAGE PACKS too, under WinXP OS. I plan to stay with the RT BNAV Browser in any event. My OLD LAPTOP hardware and WinXP OS seems to LIKE the RT BNAV Browser (ENGLISH Language ONLY). And also, RT does MAINTAIN his Browsers at a HIGH QUALITY level. NOT so sure as to what will happen with SM 2.49.5 Browser over time (future) --> https://o.rths.cf/boc-uxp/ So, this is all GOOD NEWS as I see it. THANKS again to 'VL' for this TWEAK.
  11. @Mathwiz | @VistaLover <-- https://msfn.org/board/topic/175591-enable-mp4-h264-aac-html5-video-in-firefox-on-windows-xp-without-flash/?tab=comments#comment-1123505 (Adobe) PRIMETIME CDM Plugin 'fix' for INSTAGRAM Video Playback https://msfn.org/board/topic/178259-instagram-videos-not-working-in-firefox-52-esr/page/3/?tab=comments#comment-1161357 Another (newer and easier) 'fix' for INSTAGRAM Video (This WORKED for me with (RT ST) BK55 Browser, but NOT for SeaMonkey 2.49.5 Release) Okay, so I tried both of these (above URLs) 'fixes' with SeaMonkey 2.49.5 Release Browser under WinXP OS. They FAILED to fix the INSTAGRAM Video playback problem for me. Others may have success with these fixes, even though it did NOT succeed for me. One can do a 'work around' by doing a RIGHT CLICK and choose (Menu) VIEW PAGE INFO. Then find the VIDEO 'File Type' under the MEDIA tab (2nd one). Then COPY and PASTE that (MP4 Video) URL into a (Browser) NEW TAB. Or, use that same URL and open it in (external) VLC Player or another (PotPlayer) of your choice. For me, since ENGLISH is my Language, the RT BNAV Browser is definitely preferred. Because RT did 'fix' the INSTAGRAM Video problem via his personal 'tweaking' of BNAV Browser. Unfortunately, again, RT BNAV Browser is NOT currently supporting Language Packs. https://o.rths.cf/boc-uxp/ Added: Also, RT's level of support on his Browsers is fairly AMAZING too.
  12. Okay, I did try (RT) BNAV Browser with my Spanish (es-ES) Language Pack, and it FAILED now. The Browser MENU choices are now completely missing (not visible). This was created from the SM 2.49.4 Language Packs at the time. I recall, that when I created that 'es-ES' LangPack, using RT instructions, it did WORK, as RT said. I remember that it had mostly SPANISH Menu, with ENGLISH words still now and then mixed into it. So, RT offered his LangPack FIX for BNAV Browser as a 'Quick and Dirty' minimum solution. But something must have changed in BNAV Browser, such that his LangPacks fix no longer will work. So for now, BNAV is again an 'ENGLISH ONLY' Browser situation (it seems). REGRETS if that any of my previous postings on this BNAV LangPacks issue seem MISLEADING. I will try to find and update MY MESSAGES to reflect the current situation on BNAV LangPacks. Sadly, RT would likely have to 'look at this' again for a new FIX to happen. http://www.seamonkey-project.org/releases/2.49.5 SeaMonkey 2.49.5 Browser & Emailer Release (Official) - WinXP - 2019.08.05 https://archive.mozilla.org/pub/seamonkey/releases/2.49.5/langpacks/win32/ SeaMonkey 2.49.5 LangPacks - Note: URL is FIXED here vs. 'error' one So, I tried the SM 2.49.5 SPANISH (es-ES) LangPack (Add-on), worked fine here. One bad aspect (to me) is that SeaMonkey 2.49.5 Browser does NOT support INSTAGRAM 'embedded' VIDEO playback properly under WinXP OS. https://o.rths.cf/boc-uxp/ Whereas, the RT BNAV Browser DOES support INSTAGRAM 'embedded' VIDEO playback properly under WinXP OS. Added Later: @VistaLover did make an EXCELLENT REPLY to my message, located at this URL here --> https://msfn.org/board/topic/177125-my-build-of-new-moon-temp-name-aka-pale-moon-fork-targetting-xp/?do=findComment&comment=1170250
  13. Okay, fairly sure it was 2.49.4 Language Packs that were used when RT fixed it. I will try to find time to take a look at this situation in the near future. I have a SPANISH Language Pack that is working (installed on BNAV here).
  14. *** This FIX from RT for BNAV Browser Language Packs seems NOT working anymore *** @Mathwiz --> I believe somewhere back in the bowels of this thread is a post explaining how to modify SeaMonkey language packs for (RT BNAV) Navigator. <-- @VistaLover --> Perhaps 'TR' has that link handy, since I know he's one of the few (?) users here of that (RT version of BNAV Browser) fork... <-- Okay, this should be what is desired with regard to (RT) BNAV Browser and Language Packs. https://msfn.org/board/topic/177125-my-build-of-new-moon-temp-name-aka-pale-moon-fork-targetting-xp/page/101/?tab=comments#comment-1158936 Rewrite (for clarity) of RT's Original Message to FIX the Language Packs for (Navigator) BNAV Browser. I was able to verify that RT's original instructions are correct. https://msfn.org/board/topic/177125-my-build-of-new-moon-temp-name-aka-pale-moon-fork-targetting-xp/?do=findComment&comment=1158917 RT's Original Message to FIX the Language Packs to install in (Navigator) BNAV Browser. RT (another message) notes that NOT everything is ALL FIXED, but it is good enough to use it. https://msfn.org/board/topic/177125-my-build-of-new-moon-temp-name-aka-pale-moon-fork-targetting-xp/?do=findComment&comment=1164249 Suggested (Navigator) BNAV Browser THEMES to use, instead of the DEFAULT one. DEFAULT THEME has it where Browser ACTIVE TAB is *not* a different color from other open TABS.
  15. Is there a reason that you do NOT have Service Pack 3 (SP3) installed for your WIN XP OS ??? Added Later: @dencorso (message below) did explain it for me. To each, their own.
  16. One aspect of BNAV (BOC) Browser is that the DEFAULT THEME does NOT have it where the ACTIVE Browser TAB is (differently) more brightly colored than the other TABS. I addressed that issue here at this URL below: https://msfn.org/board/topic/177125-my-build-of-new-moon-temp-name-aka-pale-moon-fork-targetting-xp/page/146/?tab=comments#comment-1164249 My view (as 'Mathwiz' said), it is a matter of preference between NM28 vs BNAV (BOC) Browsers. I have both of these Browsers installed here. And I have better luck with SP55 Browser than SP52 Browser. No substitute for 'hands on' testing? My above URL here gives reference for modifying SeaMonkey LANGUAGE PACKS to work with BNAV (BOC) Browser. RT did explain how to do it.
  17. Just giving again a THANKS to YOU for doing the 'Pulls' needed to FIX the (Menu) 'HELP' URLs related to RT's Browsers here. It is GOOD to 'head off' further complications related to 'MAT' person. Added Later: RT observed (below) of 'MAT' person --> "(He is) better (seen) using binoculars" Okay, I did LOL on this above from RT. Added Later: VistaLover observed (below) of 'MAT' person --> "(He) wants your arm and shoulder too," GOOD that my HEAD is attached ... somewhere!
  18. I would LEAVE this particular 'New Moon' current named 'THREAD HERE' to continue to exist. Because @Mathwiz did FIX some of the RT Browser 'HELP' URLs to aim HERE (THIS THREAD). And this was done, as a manner of attempting to remedy criticism from a certain 'MAT' person. Which, now that it is done, I think that the situation is MUCH IMPROVED. I would argue that RT can say to 'MAT' that what is REASONABLE to address the 'MAT' concerns, has been DONE now.. As to IF that RT wants to 'monitor' ADDITIONAL MULTIPLE THREADS created on a specific 'Unique RT Browser Defined Basis' -- SEEMS like that should be as RT PREFERS it to be. This 'THREAD HERE' is a bit messy, no question. But it does offer solutions and feedback for the various RT Browsers. But okay, NOT so easy to always LOCATE the exact MESSAGE that pertains to the specific RT Browser that you have a 'problem concern' with it. Added Later: The TITLE of this MSFN THREAD (Here) that RT created it, is perhaps NOT quite the best one. But again, (MSFN User) 'Mathwiz' did FIX (change) the 'HELP' URLs in the RT Browsers to POINT to THIS RT THREAD, as CURRENTLY TITLED. And these URL 'HELP' FIXES were done to try and satisfy concerns of a certain 'MAT' person. So, to change this RT THREAD TITLE, would cause the 'HELP' URL FIXES to NO LONGER open THIS RT THREAD properly (so a URL 'fail'). So, THIS RT THREAD here is somewhat a 'NOT Broken, So Do NOT FIX IT (Change TITLE)' situation (my view). Added Later: Amazing all that RT keeps straight in his head.
  19. I was recently helped by another MSFN User concerning Serpent ST55 Browser = Basilisk 55 by RT. Concerning getting the INSTAGRAM Video (embedded) to play back properly. I was referred to this URL --> https://msfn.org/board/topic/178259-instagram-videos-not-working-in-firefox-52-esr/page/3/?tab=comments#comment-1161357 (Note: Add this below to 'About:Config' -- Needs to be set below 56.0 for INSTAGRAM site to open) general.useragent.override.instagram.com (String) Mozilla/5.0 (Windows NT 6.1; rv:52.0) Gecko/20100101 Firefox/52.0 For myself, I had to create the Folder = "chrome" -- located inside the Folder = "Profiles" Use (Menu) HELP , TROUBLESHOOTING INFORMATION , find "Profile Folder" , click "Open Folder" button Then, I created the "userContent.css" file (via *.txt file first) inside Folder = "chrome" with this needed coding: @-moz-document domain(instagram.com) { div.ZyFrc[role="dialog"] { display: block !important; } } Close Serpent ST55 Browser, reopen, and INSTAGRAM video should work properly now. The uBlock Origin (Extension) manner (at URL above) did also succeed (work) for me too. Figured no harm to 'repost' this information. Please give a 'LIKE' at the URL listed above if you do.
  20. https://wrealu24.tv/ The above URL has a LIVE YOUTUBE CHANNEL (URL below) https://www.youtube.com/channel/UCiwsDgj8mJnsGOr6oN-2OVQ And the LIVE STREAM there is (URL below) https://www.youtube.com/watch?v=N2tHHh0YUtw http://potplayer.daum.net/ You can PLAY that LIVE URL STREAM in POTPLAYER (Stand Alone PLAYER) Here the 'playback' streaming video quality seemed like it had BUFFERING problems. It would play okay for say 4 seconds, then 'freeze' for 1 second, then resume playback. And then 'play, then freeze, then play' kept repeating itself. But I am not located near to POLAND either. Your experience may be better than mine. Just suggesting an alternative viewing strategy (stand alone PLAYER) to you.
  21. I am opposed to the idea that RT should have to 'worry' about some 'internalized' ADD ON working with his Browsers. It seems like that ADD ONS (LEGACY) can 'stand on their own' -- so LET them do that. (Evil Humor) And, @VistaLover enjoys solving SOME riddles related to 'Ghosts in the Old Machines' https://o.rths.cf/boc-uxp/ RT has some ADD ONS (*.xpi files) listed for download at his above URL for BNAV Browser. https://legacycollector.org/firefox-addons/ This above URL has Firefox LEGACY ADD ONS too. Just a straight forward download, no install involved. https://legacycollector.org/firefox-addons/722/index.html NoScript Security Suite
  22. ANYTHING that RT suggests it, defer to him. My next 'advise' likely will NOT work, because RT did NOT suggest it. But I would check this particular setting, which RT helped me awhile back suggesting it. NM28 Browser: (Menu) TOOLS , PREFERENCES , ADVANCED (Far Right Icon) , GENERAL (Tab, 1st One) (Setting Box) "Compatibility , User Agent Mode" = FIREFOX COMPATIBILITY (3 choices there) See if using "FIREFOX COMPATIBILITY" there helps. For me, here, it had CHANGED to "NATIVE" setting, and I do NOT recall changing it. But I have been using a NM28 Add-On "User Agent Switcher" too, so maybe I 'did something.' So, I just changed it 'back' to FIREFOX COMPATIBILITY again, per advise from RT in past. Does not hurt to check for this "FIREFOX COMPATIBILITY" setting. But whatever 'RT' or 'Mathwiz' says it (or 'VistaLover') -- go with them, and ignore me.
  23. You obviously make a good point. But maybe @Mathwiz deserves a 'time break' for a bit on doing more 'PULLS' with regard to these RT HELP URLs related to RT's various packages. I think that fixing the NM28 Browser HELP URLs, was likely the best choice, in terms of cutting back on 'unwanted traffic' aimed at PALE MOON websites.
  24. The above URL (from you) SEEMED to load and work okay here in the latest NM28 Browser version. But I did not try EVERYTHING with it. It had 'Build a Bundle' options and like that, fairly complex. I did NOT use those. IF you are using WinXP OS, maybe running CHKDSK.EXE would help.
  25. I just did install (update) the latest NM28 Browser, with the HELP URLs now altered to aim at RT websites. And the NM28 Browser 'Install Upgrade' Screen has been removed, so I only see a 'Globe' there now. This seems a significant improvement. I would guess that even a certain 'MAT' person might agree! Added Later: Probably, more people use the 'New Moon 28' Browser, than any other RT offering. So, that the NM28 Browser HELP URLs are now FIXED to aim at RT websites, is a MAJOR improvement. HELP URLs for other RT 'packages' (BOC EMAILER, etc), can be fixed eventually too. The general strategy for RT's HELP URLs is now a 'defined situation' in my view.
×
×
  • Create New...