Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won

  • Donations

  • Country

    United Kingdom

AndrewNi last won the day on April 20

AndrewNi had the most liked content!

About AndrewNi

Contact Methods

  • Website URL

Profile Information

  • OS

Recent Profile Visitors

979 profile views

AndrewNi's Achievements



  1. I'm using -vga std (the default) and vbemp NT version k. The performance is no mystery on my PC - I can't use any accel options because I use VirtualBox, which conflicts with them. It's all software CPU emulation. The textures are what I'm more interested in working out. On Bugs, the textures are fine on my old ATI graphics card, and in Liew's video playing GP3, he's using a Windows machine with an AMD Vegas GPU. Is it possible that the Intel GPU and Apple M1 GPU cores are missing an OpenGL extension that AMD/ATI GPUs have? Or maybe the wrapper maps them in a strange way? I admit to being very confused as to how backwards compatibility works in OpenGL. This is all fun and curiosity for me, so if Parallels works, then great! Case closed, as you say.
  2. He is? Hi Liew Do you mean "nope, I haven't tested other OpenGL programs" or "nope, it doesn't crash, they work fine"? The ReactOS DLLs are the best working ones on my system. GP3 seems to work OK with them, but I still have the missing texture thing that I also saw in Bugs Bunny. Also my computer isn't very fast at all (far removed from a $6000 machine), so it's outputting about 1fps. It's so slow in fact, the FPS counter that usually proudly appears in the console isn't there. This screenshot comes from the calibration option. Maybe it's night time... I was puzzling over commit 0dd2b2d. Normally, if you put the file mesagl.cfg in the same directory as the program, you can limit ExtensionsYear to a specific year for the whole VM. However since that commit, whenever a WGL function is called, the value is reset on purpose. I don't know if it's because I'm using Windows as the host, or if it's the guest software's behaviour, or whatever, but virtually every call seems to be a WGL function/started with one and thus the host cap is being effectively ignored. The puzzle is... why? Why ignore the cap for WGL? (Although capping the year didn't help with the missing textures.)
  3. Bruno, have you tested ordinary OpenGL programs within the guest? e.g. wglgears is often used as a demo. If you have, does it crash qemu in the same way? I expect it would still load XQuartz, though. I don't have a Mac, but on Windows as the host, it always produces a new MESAGL window when doing OpenGL passthrough work. This sounds similar to what happens with XQuartz. In keeping with the thread, I have been looking at ReactOS. The qemu-3dfx wrappers work perfectly fine within it, and if you put the opengl32 wrapper into the system directory, ReactOS' implementation of WineD3D (which seems to be around version 3.3, but with some extra patches) will pass along the OpenGL commands. ReactOS' compatibility with the Windows programs themselves is a bit hit-and-miss though, so I have isolated the WineD3D components for use on Windows XP RTM+. They even made a nice control panel applet. ReactOS' WineD3D 3.3ish DLLs: https://mega.nz/file/kcpmEJ7I#KRmaA--70ssX3-O162Yg-Dz76IXYfDlJoIKAd-jPohA As for the license thing, I thought it was quite straightforward. Wine is licensed under the GNU Lesser Public License 2.1, and it says that a fee can be charged for the binaries/sources, with no upper limit etc. As long as anyone who pays can successfully ask and receive the source code, then there's no problem. (e.g. when you buy a Linux-based router, you get the binaries in its flash memory but no source code, just a website to visit if you want it.) So this lay person (<----) highly suspects he's in the legal right. Of course, anyone who does buy them gets 100% of the rights he has too - so, for example, I could buy his product, then legally sell them to two people for $40 each and make a profit. Steady on... actually I'm surprised he didn't work out a deal with you. Instead of spreading the good word across half the web, you've spread the erm... not-as-good word. You could be like, the CEO of project advertisement, after all, I only found out about this project via your postings.
  4. Hey. So I have been following this topic for about a week, here and on Vogons. You've posted about this topic a lot, Bruno. A lot. I'm honestly thinking Liew's asking price might be good value for you. (Although I do have issues with him labelling it as a "willing donation" when there's an exact amount listed, etc.) helkaluin's builds: Wine began using the D3DKMT* APIs, which are only available on Windows Vista and above. Fun fact: even the latest dev builds of WineD3D work fine on Vista. But that's no good for XP and below. Fortunately, Wine also contains an implementation of those APIs we can link against. I have managed to build three versions of WineD3D - 4.12.1, 4.21 and 5.0.5. They are compatible with Windows XP RTM and above. They won't work with Windows 2000, 98 (not even with KernelEx) or below, not at the moment anyway. https://mega.nz/file/tBpEQbSQ#tXkiMX_b2UD8-YQbbrtfV1KOivyglORr8FF3qoyn3ek I have tested these builds on a real Windows XP machine with an ATI Radeon HD4xxx GPU, and they all work well with the standard DirectX samples (rotating teapots, spinning cubes, floating text, etc). I have also compiled qemu-3dfx and all its wrappers, with Windows 7+ as the host target. Building qemu-3dfx itself was actually quite painless, but this is where things get complicated. The characteristics of the host system are very important. I tried the Bugs Bunny: Lost In Time Demo on Windows XP RTM with WineD3D 5.0.5. Using the exact same VM HD image on two systems - ATI Radeon HD4xxx (booted into W7) and an Intel UHD 630 (W10), I got these two differing results: Intel UHD 630: ATI HD4xxx: No textures on the Intel, but perfect functionality on the ATI GPU. I also attempted to play Crammond's Grand Prix 3 Demo, since it's mentioned a lot. However, it wouldn't even start - no crashes as such, just a black screen. Interestingly, it would not work on the host Windows system either, without qemu/WineD3D involved etc. Perhaps it's just a problem with the demo, but it might also be something to do with the host GPU, which of course, propagates into qemu. (In other words, don't get your hopes up Bruno! :- ) As for "did Liew create modified builds of WineD3D?" - I'm confident he did. My evidence? ScaleWindow. See this post by kjliew on Vogons, where he describes using the ScaleWindow setting to stretch the image, because otherwise you get a small box in the corner of the window. If you scroll down the thread a bit to this post, you get to see the whole registry file with ScaleWindow included. This setting is not a part of WineD3D's source code, and it's not listed in the WineD3D registry key settings. Honestly, although this is a fascinating piece of work, and Liew obviously knows a lot about graphics APIs and GPUs etc, I don't think this is really a viable way to play games. I was testing PowerSlide via Glide, which worked fine graphically, but the truck's wheels kept sticking - something to do with keyboard inputs into qemu, I assume. I've never had a problem like that on PCem. You also get 100% DirectX compatibility with PCem, since you're using the official Microsoft libraries. Anyhow. I hope that the above libraries are of some use to somebody, and I also hope that Liew gains a sense of community spirit, because at the moment, I don't feel like his efforts are really about game preservation as he claims on his Github page.
  5. Hmm, I'm not convinced. Here's why: The tooltip for Windows Update at 1:24. The shortcut I have on my Windows Me computer doesn't have that description, it just says Location: C:\WINDOWS. However, Windows XP does have that description in its tooltip.The My Computer folder at 1:45 has the grouping of XP.The description for the disc drive is "DVD Drive". On mine (with a DVD-ROM drive) it says "Compact Disc".The icon for IE belongs to either 4, 5 or 5.5. But "Lock the Toolbars" functionality didn't come to 98/Me until IE6. The toolbars are clearly locked at 1:45 as there is no handle to the left of File or the Back button.For these reasons I think that it's either a good theme applied to XP, Me's shell on XP, or so much of Me is replaced by XP that it's not really Me anymore.
  6. You can still get the stone look in 2000, but you have to do a tiny bit of manual pixel art. Attached to this post is a screenshot of the design of the stone pattern in 98SE. In 2000, open the Display Properties and click Pattern. Choose any pattern you don't like in the list, and edit it. Copy the pattern from the 98 screenshot by clicking inside the square on the left (click once to make it black, again to white/other colour). When finished, press the Change button, then Done, then OK. Hopefully after all that you should have the stone pattern background.
  7. DeepBurner seems to start OK in my 95 OSR2 virtual machine, with shlwapi.dll version 5.50.4943.400 from IE 5.5. Maybe you need to update IE or install the shell update included with IE4.
  8. The problem is with Microsoft Works, it can't open the protected sheets within the workbook. Excel Viewer 97 will open it alright.
  9. Atlantis Word Processor supports opening and saving DOCX files, and is very light at about 5MB in size.
  10. That same problem also happens to me inside Virtual PC with Windows 98SE. It seems that running the DirectX Diagnostics Tool (dxdiag) before running Firefox fixes the issue, at least temporarily. I don't know why it does, though. Before / After dxdiag: I didn't give it any more thought since it's only a VM, but maybe szakacsze can try it and see if it helps.
  11. In Office 2000 and above you get a taskbar entry for each opened document, in Office 97 you have to use the Window menu to switch. (I assume that has something to do with 97's NT 3.51 compatibility.)
  12. Hi, the setting is under Tools -> Options -> View tab Untick "Field Codes" (towards the right side) and OK the settings dialog.
  13. I've just tried it with Office 97 SR-2. The Office 2007 Compatibility Pack installs fine, and you can open Word 2007 documents.
  14. Autopatcher can also download the XP x64 updates, allowing you to burn them to CD for offline install. That's what I used for my last install of XP x64.
  15. You get a month of usage without the key. The activation bubble will popup from the tray to remind you to activate, and when you do click on that it'll ask you to enter your key first. I assume the expiry relies on the idea that you can't activate without a valid key, and without activation after a month it will stop working until you do.

  • Create New...