Kiriko Takemura

My progress is really slow at the moment, but I do not give up (yet). The to do list on the previous page of open thing is getting a little smaller. I changed from Virtual Box to VMware for development. I can test in Windows ME now without having to use a real PC for it (Win9x on Virtual Box is terrible). But on shutdown the WinME VM hangs. Working: JavaScript alert, input, prompt, onunload, etc. handlers natively on frontend Working: File downloads in native IE downloader (goes via a small and super fast proxy that streams the download to IE while Chromium engine is still downloading it) Working: Find in page in native classic Windows search box + Chrome style hiliting Working: Basic/Digest authentication with encrypted password saving on local system Fun fact: Modern browsers fail the ACID3 test. Currently working on file uploads.

Some progress: History recorded in local IE browser Travel log working (menu inside back and forward button) CSS cursors working Flexible window resize without disconnecting/reconnecting RDP SSL validation with IE-style dialog box IE style error messages But still so much to do: JavaScript alert, input, prompt, onunload, etc. handlers Download handler Context menus Find in page Full screen mode File uploads Build in Ruffle, somehow Adblock, hopefully at least a simple one via DistillNET library Open in new window JavaScript popups Better error handling on crash of backend I really hope I can share more than pictures very soon. But still there is too much missing and I think people will complain a lot.

Some thing I have been work on in my very little free time. You know "Browservice" project right? He made a software that pushes endless stream of JPEG images to the browser that contain a website rendered by Chromium engine. Complete with fake address bar and front end JavaScript to capture keyboard and mouse. The idea sounds so ridiculous, so crazy, but it actually works on almost every OS and almost every old browser. Problem of "Browservice" is it doesn't feel convincing. IE constantly downloading images and status bar goes crazy (it appears that the memory leak exists). Also very slow when website has a animating. I did something similar but using RDP. Only for IE5 and IE6. Should work Win98/ME/2000/XP<SP3. I develop in XPSP2 IE6 and WinME IE 5.5 for now. Since it's ActiveX control, I am inside of IEXPLORE.EXE and have full control (that's how drive-by downloads installed spyware and virus back in the days). I use the power to intercept the menu, toolbar, address bar, status bar, etc. IE becomes only a bit of GUI under my control. All commands are redirected to remote server running Chromium engine there. RDP has the feature "Virtual Channel" to send messages (WTSVirtualChannelOpen etc.) My implementation so far browsing experience feels 99% like using real Internet Explorer because RDP protocol is much faster and get clipboard support, access to local hard drive, sound, video streaming, etc. for free by Microsoft. Unfortunately still very early in development. Downloads not yet work. History not yet work. Popup window not yet work (very difficult). But I hope that in a few months from now good old Win9x and Win2000 can join a modern Internet again. Backend in C#. Frontend in Visual Basic 6 with OLEEXP and patched SSUBTMR (just to prove it can be done, but it is painful). Maybe you will say that's the fake screenshot. Okay, you can do it. I don't have the argument at the moment. But soon I hope to show it running on real hardware.

Kind of, but you are in for the experience of a lifetime (but not in a good way). Debugging Win9x is not very easy if you are spoiled by modern debuggers. How good is your x86 asm skills? Mine are poor. Whatever you do, basically you will need a second machine connected to the problematic machine using a null modem serial cable. Please, consider the pinout: 9 Pins 3 2 TX 2 3 RX 5 5 GND 25 Pins 2 3 TX 3 2 RX 7 7 GND Where to find debugger: Windows 98: Win98ddk.exe (19987736 bytes) Windows 98SE: Win98ddk.exe (26377712 bytes) Windows Me: winmeddk.exe (1469056 bytes) Where to find the files in 2022? No ideas. Not at Microsoft.com, that is for sure. Anyway, Once you found DDK https://bikodbg.com/blog/2021/08/win98-ddk/ has a nice setup guide, but I replicate here because websites tend to disappear: On another website http://www.massmind.org/techref/language/asm/debugs.htm there is the information that win 2000 SDK has a nice GUI for WDEB386. I never used it though. Here is the manual for the debugger: https://anonfiles.com/61jdP7D0y2/wdeb386-debugger_pdf Someone, please mirror it because if it gets lost, the next person stopping by here will be sad. If you do manage to debug the kernel far enough to find the root cause please let Raymond Chen at Microsoft know so you can get a commemorative plaque.