Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 01/27/2023 in all areas

  1. https://github.com/win32ss/win32-api-reversals But this is not complete. There are many functions I implemented by copying over blocks of hex codes from newer DLLs, because I did not know C well at the time. There are some other functions that are too messy for me to put up ATM. Here is the installer source code (needs to be updated to support copying to places other than System32/SysWOW64, installing drivers, and adding a GUI): https://github.com/win32ss/nt6-unofficial-update-installer-engine And this tool builds a list of export pragma directives for a wrapper. It supports PE32, PE32+, and both named and ordinal-only exports: https://github.com/win32ss/export_pragma_builder
    3 points
  2. "Zip disk" is meaningless in the context of "drivers". There used to be 5 (at least[1]) ZIP disk drives, with different interfaces (and obviously difference drivers were needed for them): 1) Parallel <- normally NOT bootable 2) SCSI 3) IDE 4) ATAPI (almost same as above) 5) USB The "type the name of the command interpreter" error you are having (I presume it to be in text mode) is coming from the underlying DOS, it happens well before the Windows 95 (the GUI part) loads (and thus the needed drivers). Is the error you are having similar to this screenshot, right? https://www.betaarchive.com/forum/viewtopic.php?t=35451 If this is the case it is happening at a time when the boot is from the disk supported by the BIOS, no driver is needed/in use at this time. Either you have command.com missing or - for some reasons - the DOS cannot access the ZIP disk as C:\ (or as another drive letter, if it is not partitioned it may be A:\). This may have several reasons behind, a common one (but again it may depend on which specific Zip disk drive you are using) is the way the disk has been partitioned (ZIP disk "standard" was an active partition in fourth MBR partition table entry) or "not partitioned" (formatted as superfloppy), and in the specific BIOS you have and how it behaves in these cases, additionally ZIP disks used to have a "peculiar" CHS geometry, which may or may not be involved in the issue. It is also possible that again for *some reasons* the SYS.COM didn't transfer COMMAND.COM properly or it (or its directory entry) is corrupted. some related to ZIP disks info: https://www.win.tue.nl/~aeb/linux/zip/zip-1.html Maybe if you provide some details about the exact hardware you are using and the exact way you prepared the disk, a solution or a workaround could be suggested. jaclaz [1] a more detailed, though not necessarily complete, list is here: http://reboot.pro/index.php?showtopic=12436&p=108810
    1 point
  3. this one doesn't come with source now. binary is newer than source code.
    1 point
  4. Doesn't have anything to do with the problem, all browsers throw non-sensical errors when they encounter code they don't understand, eg.: class Lc { bus; constructor(t) { "function" == typeof t.getVersion && Rc()(t.getVersion()) ? kc()(t.getVersion()) !== kc()(this.getVersion()) && Nc.warn("Proxying an event bus of version " + t.getVersion() + " with " + this.getVersion()) : Nc.warn("Proxying an event bus with an unknown or invalid version"), (this.bus = t); } getVersion() { return "3.0.2"; } subscribe(t, e) { this.bus.subscribe(t, e); } unsubscribe(t, e) { this.bus.unsubscribe(t, e); } emit(t, e) { this.bus.emit(t, e); } } And it's becoming very common, had this kind of code in another app at work for almost a year now, if not longer.
    1 point
  5. Thanks to soggi and VistaLover ! VistaLover, you are the wise man of this forum, your explanations are very helpfull. Thanks again !
    1 point
  6. Hello Royam1, I was informed of this open source version of Chromium still compatible with Windows XP/Vista and I thought it may interest you. https://github.com/weolar/miniblink49 This launched on my Windows Vista computer but crashed when I had it go onto websites like MSFN and Youtube.
    1 point
  7. Sorry, not sure if this is really (as) correct (as I thought). Maybe it works better out-of-the-box on stock Chromium 86 on supported systems, never really tried that. I know it's not as horrible on Edge 94 (with --disable-gpu) on my Win10 as it is on 360Chrome 13.5 on my XP. I also know 60FPS video is nothing special, my car's infotainment does it without a hitch. Finally, I know Android x86 of 2020 is pretty much unusable without real graphics drivers, can barely move the mouse around, especially on low-end hardware. Its compositor should pretty much be Google's code for the most part. On the other side, I guess most of us pretty much survived some moments without a real graphics driver on fresh Windows install, from old to new.
    1 point
  8. A Massive Void Has Been Sealed Inside The Great Pyramid Of Giza For 4,500 Years. What's Inside? When pharaoh Khufu's sarcophagus was opened, nothing was inside. Could his body be in the void? by JAMES FELTON Senior Staff Writer Jan 23, 2023 Inside the Great Pyramid Of Giza, there is a massive void. The room, sealed when the pyramid was completed some 4,500 years ago, is of unknown purpose, though some have speculated it could be a secret burial chamber of the pharaoh Khufu, who ordered the pyramid to be built. In 2017, a team known as ScanPyramids scanned the Great Pyramid of Giza using muon tomography. Muon particles are negatively-charged particles produced by cosmic rays which collide with atoms in the Earth's upper atmosphere at around 10,000 per square meter per minute. "Like X-rays, which can penetrate the body and allow bone imaging, these elementary particles can keep a quasi-linear trajectory while going through hundreds of metres of stone before decaying or being absorbed," the team explains in their study, published in Nature. "By recording the position and the direction of each muon that traverses its detection surface, a muon detector can distinguish cavities from stone." All that is to say that they used a very cool way – involving cosmic rays, no less – to look inside the Great Pyramid. And inside, they found a chamber that had never been seen before. "We report the discovery of a large void (with a cross-section similar to that of the Grand Gallery and a minimum length of 30 metres [98 feet]) situated above the Grand Gallery," the team wrote. "This constitutes the first major inner structure found in the Great Pyramid since the nineteenth century."... Hidden Chamber in Great #PYRAMID as big as a PLANE Confirmed by New Scan | Egypt (6:40) MORE: https://www.iflscience.com/a-massive-void-has-been-sealed-inside-the-great-pyramid-of-giza-for-4-500-years-what-s-inside-67207
    1 point
  9. For the Lab Settings page ( chrome://settings/lab ) -- UNCHECK "use hardware acceleration" and UNCHECK "enable Data Execution Prevention". Also UNCHECK "discard background tabs", UNCHECK "reminder to optimize memory", and UNCHECK "reminder to clean cache".
    1 point
  10. So the issue is not the BIOS (in itself) nor (probably) the USB drivers (in themselves) it is a combination of the two. Pure speculation, to be checked/confirmed: Case A, stick connected before booting: A1) when legacy USB is disabled in BIOS the OS knows nothing about the USB stick and when the drivers load they load/mount the device fully A2) when legacy BIOS is enabled in BIOS the stick is mapped by BIOS and when the USB drivers load they *somehow* load/mount the device partially Case B, stick connected after booting: B1) no matter if legacy USB is enabled or disabled in BIOS, the OS knows nothing about the USB stick until the drivers load and ... (either mount the stick fully or not) In theory A1 and B1 should behave the same, but there could be a difference between the USB drivers enumerating the stick when loading (case A1) or after having already loaded (case B1). jaclaz
    1 point
  11. Sounds like there should be dramatic music here On Windows 8, I plan to stick with Firefox ESR 102, through September, and with Server 2012 updates through October. IF (and it's a big "if") Mozilla extends support to ESR 115, I will stick with Windows 8 for another year. Beyond that, I have a PC all set up with Windows 10 LTSC 2019, all ready to go, and as customized as possible. I have Classic Shell for the Start Menu, and I've used Winaero Tweaker to get it somewhat into submission. So I'm ready as can be. I will say though, I'm feeling a stir of interest over the upcoming Vista SP3. I'd be interested to see what it brings, just for interests' sake.
    1 point
  12. For those who were seeking "official" confirmation. Opera finally admits they lied . After I pressured them ? I dunno. A reminder : 96 is based on chrome 110, which I ported to Vista. https://blogs.opera.com/desktop/changelog-for-96/ "DNA-104390 Remove Windows 7, 8 support ..." https://msfn.org/board/topic/184249-chrome-110-based-opera-i-ported-it-to-vista/
    1 point
  13. I found that there are ultimately four reasons why Chromium is broken on NT 6.x: 1. New imports in kernel32 and userenv. They can all be stubbed, not hard to fix. (Vista/7; 8.x has them) 2. Use of job object APIs in ways that are only supported on 8.x (without sandbox) and 10 (with sandbox) 3. Use of new NtQueryInformationProcess class for enumerating process handles; if it can't be used, the content process will be terminated (8.0 and below, sandbox only) 4. Use of new DirectWrite factories, like IDWriteFactory3, which was introduced in Windows 10 #1 is taken care of, I'm getting there with #2 and then I should be able to do #3. #4's solution is actually quite simple; copy over a Windows 10 DWrite.dll to use with Chromium using DLL redirection methods (I used 10.0.17763.1 and I think 10240 and up should work too). Then patch these DLL names in the import table with a hex editor or CFF explorer: api-ms-win-core-libraryloader-l1-2-0.dll -> kernel32.dll api-ms-win-core-localization-l1-2-2.dll -> kernel32.dll This is sufficient to run the latest Chromium browser snapshot on Windows 8: Right now there are truly missing functions on Windows Vista and 7, in api-ms-win-core-delayload-l1-1-0.dll and api-ms-win-core-delayload-l1-1-1.dll. Some of those return function pointers so they can't be stubbed.
    1 point
  14. I got Heroic Launcher and Rare to work by adding api-ms-win-core-path-l1-1-0.dll. Heroic Launcher use Electron though, Rare might be better for the future.
    1 point
  15. Calm down, relax, drink some tea and then just hit "report" button, easy. No need to write posts on your each and every action/thought.
    1 point
×
×
  • Create New...