Leaderboard

What is ViStart? ViStart is Start Menu replacement that works with Windows XP or modern systems like latest Windows 10! This application is here for a long time, I remember back in 2007 it was very requested as fully working Windows Vista Start Menu with real search bar. During time ViStart evolved to version 8.1.5208 compiled 14.2.2016. After long delay was 31.3.2021 released version 8.1.5254 and Lee Chantrey decided to make it Open Source and released source code on GitHub Now I created fork 26.1.2023 with v8.1.5254 and during my testing I realized many features that I need are unfinished or missing. For example even with fully translated Language file translation in app was incomplete. 3.2.2023 I have released v8.1.5258 as my latest attempt to improve ViStart to another level. I started with my changes with my first release at 28.1.2023 with v8.1.5255 To make installation easy as possible I have created two silent installers for ViStart. One which handle application that is installed to %ProgramFiles% and one which extract skins related files to %AppData%. You need both of them to launch ViStart. These links always points to latest version it can be updated frequently than official release on GitHub. I have done various improvements to the code. Here is list of main changes, for more details see changelog. Improved translations, every visible element under Windows XP / Vista / 7 host can be now translated using Language.xml Added new context menu in "Navigation Pane" on custom items - Open, Rename and Hide Added new context menu to "Computer" - Manage and Search Added new context menu to "Computer" / "Network" / "Control Panel" - Show on desktop / Hide from desktop Added new context menu "Explore" when browsing All programs to be able open whole folder Removed ViPad context menu when ViPad is not running or not installed. No more "online" feature in context menu Realigned all items in Control Panel to make UI more clear Added new option to change Skins Rollover icons similar to Start Orb Skins settings Updated application icon with older better one from v1.6 era Non existent "Frequent programs" / "Pinned programs" loaded from settings.xml are not displayed Added 18 optional items than can be displayed in "Navigation Pane" from settings.xml Added Libraries, Downloads, Printers and Faxes, Set Program Defaults, Search support for settings.xml - Windows XP related options are set as default in settings.xml - Added Games folder support which points to %ALLUSERSPROFILE%\Start Menu\Programs\Games - this is not dynamic and on each XP language you need to manually fix this path in settings.xml if would like to use this option - Windows Vista / 7 options Libraries, Downloads, Games, Help are commented out, you need manually fix settings.xml on other systems than XP / 2003 Added Windows XP Luna Blue, Windows XP Luna Olive, Windows XP Luna Silver, WIndows XP Embedded, Windows XP Zune, Windows XP Royale, Windows 8 Beta Concept, Windows Vista, Windows Vista 5270 Skins Added option to control "Navigation Pane" display items limit, see Windows 8 Beta Concept Skins layout.xml ViStart translations are now really unfinished as everything is now translatable. But I adapded all languages founded over internet and all of them are included. Feel free to improve current translations or provide new one! Every language have all needed strings inside to make it easy for you, translators! Brazilian Czech - 100% Dutch English - 100% French German - 90% Hebrew - 100% Italian Korean Polish Russian Spanish Turkish Download ViStart-all.exe https://www.mediafire.com/file/bgra4u1jgh02v1j/ViStart-all.exe/file ViStartSkins-all.exe https://www.mediafire.com/file/a2tw9bj6pph2my4/ViStartSkins-all.exe/file Preview Currently included Skins Windows 7 Start Menu Windows Vista Windows Vista 5270 Windows XP Luna Blue Windows XP Luna Olive Windows XP Luna Silver Windows XP Royale Windows XP Zune Windows XP Embedded Windows 8 Beta Concept Ideas and improvements that come in future releases Windows 11 support Skins SubSkins support - Skins creator can specify Skins variants, like different Start Menu size or Light / Dark mode etc. I have currently implemented these changes which were accepted by author to merge into main ViStart branch. Changelog ViStart v8.1.5258 [*]Removed broken fix for bug 2] in "No programs match the search criteria" is never displayed "No programs match the search criteria" is never displayed #10 as it caused issues [*]Removed start_button.png depency in FileCheck, now can be loaded skins without start_button.png [*]Added new option to select custom Rollover, place _rollover directory near _skins and put your favourites rollovers inside [*]Updated Language files with latest strings [*]Updated default settings.xml [*]Added support to display "Search" option in Start Menu [*]Increased settings.xml items limit to 18 [*]Added Windows 7 Rollover [*]Added default Start Orb ViStart v8.1.5257 [*]Fixed "Files" string translation doesn't work "Files" string translation doesn't work #8 - "Files" string translation doesn't work #8 [*]Fixed Bug 2] "No programs match the search criteria" is never displayed "No programs match the search criteria" is never displayed #10 - from "No programs match the search criteria" is never displayed #10, Bug 1] still remains [*]Fixed incorrect translation loading on ViStart Control Panel for "strStartViStart" and "strStartWinMenu" [*]Improved "Pinned programs" loading from settings.xml, non existent items are not displayed [*]Improved "Navigation pane" limit again. 17 items are choosable and are parsed from settings.xml, now in Each Skin's layout.xml can be specified limit which should hide items that can't be displayed. For example user preconfigure 15 items to be displayed in Start Menu "Navigation Pane" in settings.xml. But I have specified in My Skin layout.xml which will hide 4 last incompatible items when is performed Skin change. User can always break this rule when manually selecting Start Menu default items visibility. This tweak is here to improved initial skin load to avoid buttons overlap [*]Realigned almost all items in Control Panel to make UI more clear [*]Changed various English labels according to UI polishing [*]Added option to disable Splash Screen [*]Added Turkish + Polish translation created from old various finds [*]Updated all languages with all needed strings [*]Added Windows XP Luna Blue Skin, Windows XP Luna Olive Skin, Added Windows XP Luna Silver, WIndows XP EMbedded, Windows XP Zune, Windows XP Royale, Windows 8 Beta Concept, Windows Vista, Windows Vista 5270 Skin - Start buttons needs to be created, feel free to improve these Skins I'm not graphics guy. In many Skins are correct credits. For some themes I don't know from where was found original images that was touched when adapting for ViStart 8.1! [*]Added fixed connect.png to Windows 7 Start Menu roolover instead of Homegroup icon [*]Added PNGs for Printers, Downloads, Libraries and Userfolder rollover to Windows 7 Start Menu ViStart v8.1.5256 [*]Removed "Recent" word from Skins/Windows 7 Start Menu/startmenu_expanded.png [*]Removed ViStart.manifest [*]Added ViStart.exe.manifest [*]Updated application icon with older better one from v1.6 era [*]Improved "Frequent programs" loading from settings.xml, non existent items are not displayed [*]Increased limit from 12 to 17 items in Start Menu "Navigation pane" [*]Added Libraries, Downloads, Printers and Faxes, Set Program Access and Defaults support for settings.xml [*]Added new default settings.xml into main directory and RES - Windows XP related options are defaults - Added Downloads folder support (Downloads folder must be placed in CLSID {450D8FBA-AD25-11D0-98A8-0800361B1103} know as My Documents , so this is dynamic for all languages when you create Downloads folder - Added Games folder support which points to %ALLUSERSPROFILE%\Start Menu\Programs\Games - this is not dynamic and on each XP language you need to manually fix this path in settings.xml if would like to use this option - Fixed Help and support option - Windows Vista / 7 options Libraries, Downloads, Games, Help are commented out, you need manually fix settings.xml on other systems than XP / 2003 [*]Added all needed strings to all language files. Fully translated in only Czech.xml until translators finish other languages ViStart v8.1.5255 [*]Improved translations, every visible element under Windows XP host can be now translated using Language.xml [*]Added new translatable elements into all available languages [*]Added Czech.xml [*]Added new context menu in NavigationPane on custom items - Open, Rename and Hide [*]Added new context menu to "Computer" - Manage, Search [*]Added new context menu to "Computer" / "Network" / "Control Panel" - Show on desktop / Hide from desktop [*]Added new context menu "Explore" when browsing All programs to be able open whole folder [*]Added Windows XP Luna Blue theme [*]Removed ViPad context menu when ViPad is not running or not installed. No more "online" feature in context menu [*]Removed More themes and More Orbs online buttons. No more "online" features from Settings [*]Realigned buttons on Style configuration page [*]Realigned elemens on About page and added current build visibility [*]Updated settings.xml with new defaults [*]Fixed "No skins available", if doesn't exist %APPDATA%\ViStart use current EXE dir if _skins folder exist there

If you have tried to install Windows 7 on a Surface Pro, or a UEFI-only device., you may have noticed it hangs on "Starting Windows" or gives error 0xc000000d, or you might have seen the following message: However, this article proves that it isn't impossible to achieve this. This tutorial shows you how to install Windows 7 on a Surface Pro. This tutorial is meant for the Surface Pro 1, but could work on any other UEFI-only device, which it should, but not guaranteed. INSTRUCTIONS: 1. Boot the USB. This ISO uses a Windows 10 PE, but has a Windows 7 install.wim. 2. Open command prompt by pressing "Shift+F10" 3. Type in setup.exe /noreboot 4. Go through setup normally. 5. On the command prompt, type in "diskpart" 6. Type in the following commands: sel dis 0 lis par sel par 1 (where your boot partition is) assign letter w exit 7. Open up Notepad, and click "Open" or "Save As". Enable all files to be viewed. Go to W:\EFI\Microsoft\Boot and copy the BCD file and paste it onto the Windows 7 partition. 8. Go back to diskpart by typing "diskpart" in 9. Type in the following commands: sel dis 0 sel vol w form quick fs=fat32 exit 10. Go back to Notepad, and click "Open" or "Save As". Enable all files to be viewed. Go to the USB drive, then go to the FlashBootPro folder, then copy the "EFI" folder. 11.Go to W:\ and paste the EFI folder. 12. Go to the Windows 7 partition and cut "BCD". 13. Go to W:\EFI\Microsoft\Boot and paste "BCD" on the folder. 14. Reboot. Setup should continue normally. NOTE: For some reason, Windows will NOT boot if any USB devices are connected. Any time you boot into 7, you MUST disconnect them, boot into 7, then connect them again. Wifi is integrated but doesn't work. You will need to purchase a separate USB wireless adapter. Proof of Windows 7 installed on Surface Pro 1:

Good ! Victory ! I was able to put an upvote to your post in another topic ! Here looks like I'm still blocked.

@mina7601 Btw, I'm partially involved in improving some of the designs made by others for the ViStart start menu designs. I'm also open for feedback regarding that btw.

Nope

I have installed Windows 7 on 300-500 series chipsets and Ryzen 1000-5000 processors, I myself have Windows 7 installed on a Ryzen 5950 with X470 chipset. The problems are standard for all new PCs, you need to integrate USB3 drivers, and if installing on NVMe, updates or drivers to support them. Also the installation disk needs to be made of 10 to have USB3 and NVMe support. Problems happen with G series processors, with integrated graphics, some motherboards won't install 7 while integrated graphics are on. I have not yet tried it on AM5 socket systems, although there are screenshots on the Chinese forums with 7 installed on the 600 series chipset and Ryzen 7000.

It's not just UXP they're targeting either. This undoubtedly exterminates Discourse on MyPal 68 too, since FF didn't implement this particular bit of Googledygook until FF 71. (And correct me if I'm wrong, but I don't think FF/MyPal 68 will load "legacy" FF extensions like JustOff's; so MyPal 68 is completely out of luck. At least UXP has a workaround.) What a load of, well, you know. As if they can't even make Discourse work unless they use the latest Googledygook! Explains something I've wondered about from html5test.com: Never could understand how UXP managed to support VP9 but not VP8. Turns out, it does support VP8; it just doesn't "think" it supports VP8!

I'm doing this right now!

I'm (truly) sorry to hear that. Start now and wash away the burden on those 2 strong shoulders as you are not meant to take on the troubles of the world, only your own little bubble, so maybe meditate or prayer to ask for strength and healing energy. Palms up and look up never look down, only to tie shoes lol. ....

Meanwhile on the Pale Moon forum. It's obvious Moonchild did not check the code at all. Heck, you don't need to dig into the code, it's very simple to make an actual test. Even just typing document.createElement("video").canPlayType('video/webm;codecs="vp8,vorbis"'); in the console would reveal something's not right.

I liked your posting ( I can react to postings today ) but only because you opened up and not that you're suffering.

Sort of hard for me to say anything helpful as that would be hypocritical of me as I feel the same right now. I'm just existing and not "Living". I am a bad example of a MAN.

Good, please don't and I'm glad to hear your experience was bad with alcohol. Avoid it.

I didn't find it funny, but glad I made you laugh. There's no CSS, it's set in the script through the call to the PIXI library. fps-compare-html5.html, line 170. The idea behind is that resizing frames is costly, though on the other hand, larger resolution results in having to decode larger frames. YMMV.

My result's here. What seems to work best here - go fullscreen, match the video resolution with screen's resolution, keep the mouse off the video / don't move it, rendering controls slows things down. First 20 dropped frames were from rendering controls at the beginning before they disappeared. Though this is from my budget gaming PC from 2009 with a GPU from 2014 (the latter fact probably doesn't change much in this case). Yes, but this is very simple to render. Only 48 FPS unless I decrease the window size. Same. It probably works on newer OS with compositor (having compositor is recommended for smooth animations). At least it works on vanilla Pale Moon on Windows 10 here. Add this to 360chrome.exe launch parameters: --user-data-dir="%USERPROFILE%\Local Settings\Application Data\360Chrome\Chrome\User Data" Though I prefer to add LOCALAPPDATA to user environment variables (only needed on XP which doesn't support it natively: My Computer->Properties->Advanced->Environment Variables) and set it to: %USERPROFILE%\Local Settings\Application Data Then I can use --user-data-dir like so: --user-data-dir="%LOCALAPPDATA%\360Chrome\Chrome\User Data" So the Target field in shortcut's properties pointing to 360chrome.exe would look something like: "C:\Program Files (x86)\360Chrome\Chrome\Application\360chrome.exe" --user-data-dir="%LOCALAPPDATA%\360Chrome\Chrome\User Data" The shortcut may be placed on the public desktop / start menu->programs folder, then everyone will have it that way by default, presuming they use the shortcut.

The new Inventory system works now on all Windows versions. The last update available is from March 2002 on Windows NT4.0.

Regarding the recent discussion about discourse-based forums being BROKEN under UXP-based browsers (NM28/St52/possibly also St55/moebius), I found a related thread in the official PM forums: https://forum.palemoon.org/viewtopic.php?f=70&t=29327 The point in the thread where the recent breakage happened (i.e. implementation of the "??=" operator by Discourse) is this one ; the approach savvy members there took to address the breakage is to use JustOff's Modify-HTTP-Response (legacy) extension below: https://github.com/JustOff/modify-http-response/releases/tag/1.3.8 Once installed, go to "about:addons" and access that extension's options; locate the "Filters" input field; in the initially empty field, paste the code below: [["/global\\.discourse-cdn\\.com|community\\.(frontrowcrew|cartalk)\\.com|forum\\.(manjaro|openwrt)\\.org|forum\\.italia\\.it/",["/browser-detect-/",["/.*/g",""]],["/vendor-/",["/(t\\.discourse\\.hoisted|t\\[e\\]|r)(\\?\\?|\\|\\|)=(\\{\\}|\\[\\])/g","$1$2($1=$3)","n??=[]","n||(n=[])"]],["/discourse-/",["e.draft||=t.draft","e.draft||(e.draft=t.draft)","/(t\\.__registry__\\._typeInjections\\.service|[ne]|f\\[e\\])(\\?\\?|\\|\\|)=(\\[\\]|\\{\\})/g","$1$2($1=$3)"]]]] NB: You'd better use a proper code-editor to copy/paste, to avoid any errors... Then "tick" the "Enable" setting above the "Filters" input field... @msfntor : If you now visit https://community.brave.com/ in your UXP-based browser, (hopefully) the forum will load OK (it does here, with St52): I do hope you're happier now ... The inner-workings of the method is that the extension intercepts the UXP-incompatible JS code sent by Discourse and then transpiles it on-the-fly, based on the Search-and-Replace RegExp filter specified... All credit for the filter code belongs to PM-Forum members Kris_88 and adoxa ... @Art7220 : The procedure I detailed above seems to also work for your "own" Discourse-based forum: https://forums.mst3k.com/

Fix Russia's behaviour on the international arena.

mostly peaceful chinese balloon https://www.bbc.com/news/world-64514120

New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rthost.win/boc-uxp/mailnews.win32-20230204-485bba73-uxp-a234f6917-xpmod.7z BNavigator Win32 https://o.rthost.win/boc-uxp/bnavigator.win32-20230204-485bba73-uxp-a234f6917-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/boc-uxp/tree/custom * Notice: the profile prefix (i.e. parent folder names) are also changed since 2020-08-15 build, you may rename their names before using new binaries when updating from builds before 2020-08-15. -- New build of HBL-UXP for XP! Test binary: IceDove-UXP(mail) https://o.rthost.win/hbl-uxp/icedove.win32-20230204-id-656ea98-uxp-a234f6917-xpmod.7z IceApe-UXP(suite) https://o.rthost.win/hbl-uxp/iceape.win32-20230204-id-656ea98-ia-93af9a0-uxp-a234f6917-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/icedove-uxp/tree/winbuild https://github.com/roytam1/iceape-uxp/tree/winbuild for UXP changes please see above.

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20230204-3219d2d-uxp-a234f6917-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20230204-3219d2d-uxp-a234f6917-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20230204-3219d2d-uxp-a234f6917-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20230204-d849524bd-uxp-a234f6917-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20230204-d849524bd-uxp-a234f6917-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20230204-d849524bd-uxp-a234f6917-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win64-git-20230204-d849524bd-uxp-a234f6917-xpmod.7z Official UXP changes picked since my last build: - Issue #1382 - Remove incorrect assertion. (8f3badf88) - No issue - bump default platform UA compatibility mode to 102.0 (d89f4e145) - [xpcom] remove incorrect assertion. (8bf892d72) - Issue #2083 - Part 1: Make RegExpShared a GC thing. (3796c7c1e) - Issue #2083 - Part 2: Remove use of RegExpGuard. (d163d08cb) - Issue #2083 - Part 3: Fix RegExpShared rooting hazards now it's a GC thing. (2ac60a27c) - Issue #2083 - Part 4: Give RegExpShared a finalizer. (9824659d3) - Issue #2083 - Part 5: Fix memory leak in RegExpObject. (b7e453086) - Revert "Issue #1382 - RegExpShared::groupsTemplate_ cannot be a GCPtr since RegExpShared is managed by C++" (233802c9a) - Issue #2089 - Shrink Promise instances from 8 to 4 slots by moving debug information to an external object (ed8af362b) - Issue #2089 - Only create result Promises in Promise#then and Promise#catch if it's used or the creation is otherwise observable (6e2201d3a) - Issue #2089 - Turn AsyncGeneratorResumeNext recursion into iteration to avoid stack overflow (55eacd43a) - Issue #2089 - Optimize Promise.then and Promise.all/race with default resolving functions (9744b0c2b) - Issue #2089 - Don't use BlockOnPromise fast path with non-default resolving functions, combine default resolving functions flags (ee395231d) - Issue #2089 - Improve Runtime perf of Promises (1fd51e14f) - Issue #2089 - Add a PromiseCapability struct, directly initialize dense elements in PerformPromiseAll using NewbornArrayPush (c0b1bf7e1) - Issue #2089 - Create a shared helper for PerformPromiseRace, PerformPromiseAll and PerformPromiseAllSettled (5ff7a51da) - Issue #2089 - Further runtime perf improvements for PromiseState (078daa705) - Issue #2089 - Report unhandled rejection for optimized away promise (a215929a3) - Issue #2083 - Follow-up: RegExpShared::source should be a GCPtr. (22dc363c3) - Issue #2099 - Remove unnecessary cast in GeneratorObject::suspend's do loop. (10ef0da5a) - Issue #2089 - Add cache for Promise property lookups (92906d4da) - Issue #2089 - Move ErrorObject parts from jsexn.cpp to ErrorObject.cpp (209c8e06a) - Issue #2089 - Implement AggregateError (61c99bf6c) - Issue #2089 - Rename shared Promise combinator functions, with helpers for element functions (9fc50a992) - Issue #2089 - Implement the Promise.any combinator (f75e9d944) - Issue #2103 - Fix typo in RegExp Parser (8d3f23ed0) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. My changes picked since my last build: - reverting rev 22dc363c and 233802c9 for now since I got a crash in destructor of RegExpShared. (7faa37b7d) - revert last rev (7faa37b7) and revert rev b7e45308 and 9824659d instead. (4475b2d9f) Update Notice: - You may delete file named icudt58l.dat inside program folder when updating from old releases. * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.

I would not classify this as decisive. It could be something as simple as "Installer Version A" looks for an update (via internet) and decides for itself to NOT install "Version A" but fetches "Version B" instead. DISABLE your internet connection before doing ANY install. Good Rule of Thumb because MOST installers "phone home" in some sort of way.

Someone mentioned webcompat.com, f****** WORTHLESS unless you spot an issue in Chrome, Chrome, or Chrome. I even linked well-written technical explanation by Moonchild... https://github.com/webcompat/web-bugs/issues/117488

I would say: yes. SeaMonkey does have reason for its minor version numbers. $GeckoVersion - 3 = SeaMonkey's minor version.