Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 02/17/2021 in all areas

  1. WinNTSetup 4.5.0 Final - Dropped 32-Bit version, system requirements are now Windows 7x64 + - VHD functions no longer uses diskpart.exe - VHD Attach / Detach supports ISO files - VHD Creation supports GPT Partitionsttyle - VHD Install will always create internal boot files depending on partition style - new default VHD creation type MBR - BIOS/UEFI - added VHD command line options /gpt and /mbr - fixed instant VHD creation cylinder bug - fixed iso mount does not select install.swm - Fixed open file dialog pattern not working on default WinPE 3.x + - Fixed wimgapi capture build number on H2 Systems (19041 instead 19042) - Support multiple "-regtweaks" cmdline switches - Workaround Win10 MessageBox Font bug - added ini option [vhd] bootpartsize - new ini option "RemoveBootMountsOnExit" - ini option BootMountExclude supports Vendor name - rewrote all file and registry recursion functions to use iteration - command line VHD creation uses expandable by default - command line VHD ignores disk size for expandable type - removed NT5 uxtheme patch - DPI-Awareness for Imdisk - Darkmode and DPI-Awareness for Bootice - ARM64 password reset - fixed ARM64 uxtheme patch
    3 points
  2. Here's a quick guide on how to use the "official Pale Moon portable" version as a "loader" for Roytam releases. I use the older portable versions but the process is the same if you use a newer portable version (I don't like the icon color behavior in Win10 on the newer portable version but that's just a matter of personal preference). I use both the 27.9.4 version and the 28.2.2 version. I cannot find a link for the 27.9.4 but here is where you can find the 28.2.2 -- http://archive.palemoon.org/palemoon/28.x/28.2.2/Palemoon-Portable-28.2.2.win32.exe But there is no real reason to avoid the "new" if you prefer that route -- https://www.palemoon.org/download.php?mirror=us&bits=32&type=portable (ie, from here - https://www.palemoon.org/download.shtml#Portable_versions ) When you execute it, nothing is "installed" (ie, no registry changes, for example), it's simply just extracted (you could extract via 7-Zip or any preferred archiver, if you prefer). It will ask "where" to extract the files to - I generally create a new folder named "BasePortable" on the desktop just for convenience. This folder will contain six sub-folders (Backups, Bin, Downloads, Lib, ReadMe, and User). It will also contain two files, "Palemoon-Portable.exe" and "Palemoon-Portable.ini". We'll just keep default .ini settings for the sake of this tutorial. Open the "Bin" sub-folder. There will be a sub-folder inside it called "Palemoon" - we will keep it by that name even if we are using this for Basilisk, ArcticFox, New Moon, Mypal, et cetera. Open that "Palemoon" folder and DELETE all of the files in it (if your File Manager reports a read-only file, confirm in order to delete all of the files). The "Palemoon" folder should now be EMPTY. Now browse back to the folder where you extracted "BasePortable" (I used the desktop). Make as many copies of this folder as you want in order to make several portable browsers. But keep the "BasePortable" (with the EMPTY "Palemoon" folder) for future use if you like testing lots of Roytam builds without effecting your "everyday browser". As an example, let's say we want a Pale Moon 27 browser, a Pale Moon 28 browser, and a Basilisk 52 browser. We would copy the "BasePortable" THREE TIMES. Then rename the three copies to, for example, "PaleMoon27Portable", "PaleMoon28Portable", and "Basilisk52Portable". The folder name can be anything you want it to be. Next we download the Roytam versions we want to make as a portable browser. For this tutorial, I'm using the following three - http://o.rthost.win/palemoon/palemoon-27.9.1a1.win32-git-20180707-54887c52d-xpmod.7z http://o.rthost.win/palemoon/palemoon-28.1.0a1.win32-git-20180922-3c04affe2-xpmod.7z http://o.rthost.win/basilisk/basilisk52-g4.4.win32-git-20190727-9b0ff0e8b-xpmod.7z Then all three of those .7z files are extracted into their own folders. If you use 7-Zip context menus in your File Manager, highlight all three, right-click, hover over 7-Zip, then select Extract to '*\' These will all have sub-folders of their own of either "palemoon" or "basilisk" for these examples. Open the 27.9 folder's "palemoon" sub-folder and copy all of the folders and files. Paste those copied folders and files into the "Bin" -> "Palemoon" folder of "PaleMoon27Portable". Open the 28.1 folder's "palemoon" sub-folder and copy all of the folders and files. Paste those copied folders and files into the "Bin" -> "Palemoon" folder of "PaleMoon28Portable". Open the 52-g4.4 folder's "basilisk" sub-folder and copy all of the folders and files. Paste those copied folders and files into the "Bin" -> "Palemoon" folder of "Basilisk52Portable". For the case of the Basilisk52Portable, you will also need to rename "basilisk.exe" to "palemoon.exe". Once you become more comfortable with the .ini file and the folder structures, you don't need to keep the generic default "palemoon" naming scheme. But it's easier to just keep "defaults" if new at the portable loader. You now have three browsers completely independent of each other. You can execute all three at the same time. You execute the "portable" browser by executing (or shortcutting to) "Palemoon-Portable.exe" in the root folder of each browser. This method will start new profiles for each browser. The profiles are independent of each other. The profile locations for these three examples are as follows - PaleMoon27Portable -> User -> palemoon -> profiles -> default PaleMoon28Portable -> User -> palemoon -> profiles -> default Basilisk52Portable -> User -> palemoon -> profiles -> default Hope this is helpful to those that reached out requesting more details for the "portable loader".
    1 point
  3. in real life 9x need just bit patches: - ESDI506.PDR from BHDD or TBP, and/or AHCI.PDR if ur machine work in ahci mode; - RLP; - NUSB; - "-p i" switch for incompatble acpi bios; - directX,. video and sound; all other - garbage. if u talk about this machine: http://www.notebookreview.com/notebookreview/acer-aspire-1690-review-pics-specs/ then machine look as fully compatible... get AIDA64 https://www.aida64.com/downloads run it under 98 (not XP!), select Report/Wizard/Custom/uncheck All but Devices (other get bsod)/Plaintext, save to file, compress with zip and upload here... then i try find really needed drivers for u.
    1 point
  4. = Arachne for (some) Encrypted Websites = Spent too much time on this so sharing notes. If you want to browse the internet using DOS highly recommend Links or Lynx browsers. These browsers are solid, load HTTPS pages without issue and have their own Windows 9x Member Project page on this forum. By comparison, Arachne hasn't been updated since 2013, remains buggy and by default can not load HTTPS sites, which today is most of the internet. The easiest way to access encrypted webpages in Arachne is by bookmarking a 3rd party proxy site. It's a man-in-the-middle and not secure but you're probably just using Arachne for hobby or educational purposes anyway. Alternatively, the steps below allow using Arachne to access (some) encrypted websites. For example, this forum loads fine but Wikipedia fails. So really this is just a learning experience, use the alternative browsers mentioned above for serious DOS browsing :) 1. Install and setup Arachne v1.97 (2013), available at the FreeDOS site or http://www.glennmcc.org. Arachne can be setup by running 'arachne.bat', aferwards just launch with 'arachne -r' (resume). The remainder of the steps below assume the system has a working DOS packet driver and a functional Arachne browser. If you need a DOS mouse driver CuteMouse is good, also available at FreeDOS. 2. Install CWSDPMI, required to Wget HTTPS pages. http://sandmann.dotster.com/cwsdpmi/ 3. Subsequent Arachne startups should consist of loading a DOS mouse driver, loading the packet driver, loading CWSDPMI with the permanent switch (CWSDPMI.EXE -p), then launching Arachne (arachne -r). A batch file makes this easy, example below. C:\DOS\CTMOUSE.EXE /R2 C:\DOS\LNE100\LNE100TX.COM 0x60 C:\DOS\CWSDPMI\CWSDPMI.EXE -P C:\DOS\ARACHNE\ARACHNE -R 4. Open Arachne to the Arachne Package Manager packages page. As mentioned, Arachne is buggy. If the browser is setup properly and an HTTP only page fails to load press 'r' to reload (you may be using this a lot). http://www.glennmcc.org/apm 5. Select (to install) 'wgetssl2.apm' (858345 bytes), exit then restart Arachne. 6. Attempt to load an HTTPS page, such as https://msfn.org/board/forum/8-windows-9xme. An error message will indicate 'Unknown protocol in URL' and 'The requested protocol is not yet supported'. 7. Press F2 (save or send document shortcut), which provides some popup prompts. Click 'Get SSL page or post data via SSL using Wget'. The Arachne browser will exit and Wget will attempt to fetch the page. This (old) Wget may fail with 'Unable to establish an SSL connection'. Hopefully it will, however, succeed and then when prompted 'Press any key to continue...'. Arachne will restart, rational for using CWSDPMI.EXE with the permanent switch, and the web page will display. Attempts to find a more recent Wget for DOS with SSL support were not successful. The above process is tedious. An Arachne update to seamlessly and reliably load encrypted sites is welcome. Bonus tip upon initial browsing with Arachne, Google search still works with HTTP only (http://www.google.com).
    1 point
  5. Hi, I wanted to share my experience of running Windows 8.1 on Dell inspiron 15 3567 with 8th gen i3. I honestly did not expect this but after 40 hours of searching for all drivers, the system works amazingly well. Compared to Windows 10 the battery last around 6-7 hours compared to just 4. It also is more snappy. Even though there is no official support and no official drivers, the laptop is rock solid. Never had any bluescreen, nothing. I'm just wondering how windows 10 can be possibly worse when it has all the support (from dell, intel etc..). Ram usage is also lower on 8.1. Came from 3.7gb to just 1.6 gb. Btw that 3.7gb figure was taken from clean install of windows 10 (no preinstalled dell bloatware). Also I can set display brightness independently (like when the computer is on charger or running from battery). That did not work on Windows 10. On Windows 8.1 there is no random "Fan ramp up" when the computer is running idle or playing videos. I tried windows 7 but unfortunately dell locked windows 7 in bios. It actually says that windows 7 is not supported on this device and bios prevented it from booting (very strange in my opinion). I have picture of this behavior if anyone is interested. Windows 8.1 is running on this device since november 2020 btw.
    1 point
  6. here is my device manager: https://prnt.sc/yepa6c Aside from the fingerprint driver (there is modding group working on it) everything is installed. The uhd 620 does not have official driver but I found some folks modding the kabylake one.
    1 point
×
×
  • Create New...