Jump to content

All Activity

This stream auto-updates

  1. Today
  2. No clue from me. I technically never heard of "IoT" until this thread. I run LTSC (and LTSB, both from work) and it doesn't show "IoT" anywhere. The "IoT" shows it as in "Notification Mode", something else I've never heard of. It's just inside a VM for me, just for the sake of this thread. I'm not going to "activate" it out of fear even attempting to do so would "break" my company-provided activation (which also requires our company VPN). But I guess my thoughts would be this: if this "IoT" upgrade path is questionable (it probably is, no clue myself), it's probably no different than the "upgrade path" to XP's POSReady 2009. Something I myself see as ILLEGAL and never ran on any of my XP machines.
  3. I wouldn't have recommended that upgrade path either and gone with a clean install. Windows 10 build 10586 (th2) is an internal pre-RTM build of Windows 10
  4. I am curious about this "upgrade" mentioned, as I don't believe that IoT Enterprise LTSC has any upgrade path. It *is* true that it is possible, as I had taken about 3 months to figure out how to upgrade from Win7 to it but it is NOT designed to do that. 1809 version is the oldest I would use. I have that on my gaming computer and my old work notebook. I use 21H2 on my dev notebook. I previously had lag issues similar to what was mentioned on my gaming computer at various times but only when write operations were occuring, such as when a background process was running an update, Windows Update or Steam, etc. The culprit ended up being the SSD I was using having a write speed bottleneck. When I did my upgrade, I was using a Crucial SSD and upgraded on that, but then cloned it to a Sandisk SSD. The issue occured on the SanDisk SSD only. May not be relevant but it took me a lot of tooling around in the OS only to discover the OS wasn't the issue.
  5. If you said about error in some software you had to describe exactly error in software, not behaviour of hardware. If you have error in himem.sys then take patched version (one of the two "preferred", of course) and just replace %windir%\HIMEM.SYS (or anywhere you want). >if you know whether "patcher9x" package includes all fixes from rloew's patchmem not all fixes, but all essential
  6. The driver is supposed to support Windows 98 first edition in that I don't use any of the WDM APIs that are only available on later versions of Windows (such as Kernel Streaming Events) but there are known bugs with the WDM audio implementation on 98 FE such as sample rate and bit depth conversion not working, and problems with the Sound Blaster emulator driver. Microsoft doesn't recommend the use of WDM audio drivers for 98 FE. DirectX 8 and newer update some of the Windows Kernel Streaming audio components to support DirectSound. The DO_POWER_PAGABLE error could be printed by another driver you have installed or it could be 98 FE's immature ACPI implementation. I haven't tested much on 98 FE.
  7. Yesterday
  8. As such Volume Control initiliazed without problems during install and worked for me (WinPlay3 has no volume slider). Good idea, I will try to test. But to me it seems DirectX related, not there in the N68 log's with the original DirectX 5 on that board (as far as I can see). I will try to install higher DirectX versions one by one on the N68 installation, to see if there is a version-relation. Or is your driver not supposed to support Windows 98 FE? In that case my testing makes no sense. Just thought it could be of some use to you. Personally I was interested to see if your Headphone polling was working with HDAWDM.021
  9. ok but also XMS driver could not be loaded / command.com, etc. is that normal too? btw, this isn't same topic but i was wondering if you know whether "patcher9x" package includes all fixes from rloew's patchmem, or does one need to install patchmem before patcher9x in certain situations. patcher9x notes does reference certain portions of adding patchmem, but im not sure if that means everything from it - https://github.com/JHRobotics/patcher9x
  10. Stick your head in the sand. My head is held high. You are an arrogant a ss. I have no fear in saying so. Try to ban me if you think this is all "just me". Multiple members see you as an arrogant a ss. I'm just "don't care" enough to be the one to tell you. Call it "only me" all you want. The rest of us all know the reality outside of your own head. But yeah, we've carried on enough and we've both said our piece. But one last item, speaking solely as me, YOU ARE AN ARROGANT A SS that LOVES to hear himself talk. Hey, what can I say, "it takes one to know one", because I can say (and have had others say) the same about me. DON'T CARE.
  11. @reboot12 My Clover (UEFI)'s config.plist... https://www.mediafire.com/file/sgrjiyvyi0s9eez/config.plist/file
  12. In a way, I feel a bit sorry for you. You’re incapable of speaking for yourself and need to refer to others to give your words some semblance of weight or credibility. That’s truly pathetic. And if you have even the slightest notion that your opinion of me means anything to me, I’m afraid I’ll have to disappoint you immensely. I’m always pleased when someone is well-disposed towards me, but if they aren’t, I couldn’t care less. I have my own opinion and know exactly what I’m capable of. And a healthy sense of self-confidence was practically instilled in me from birth. I really do feel sorry for you. Right then, and now, after this lovely little chat, I’m going to get back to my projects to make up for the time I’ve wasted.
  13. It's even worse for my case... because I don't even know how to run acpi ssdt tables .aml from Clover to ensure that my controller is powered on.... (Windows OSI version limit thanks to firmware, it enables and disables values according to OSI) use the SLIC tool to check what acpi tables XP does load for you and check for all informations of your device in the ACPI tables (if it's on a acpi table not loaded by XP, then that explains the issue too). Until then, no ACPI I2C enumeration works for now (mostly my case, yours may just need correct MMIO mapping IDK), not even for me (unless I fake it by enumerating it directly from i2cctrl instead of ACPI, but that would be a fake/virtual device and not the real thing, i'd rather focus on the real device than a virtual device). Keep in mind that this driver was intended to be used on XP (it's adjusted to what it can do on XP) and not on later versions (meaning that it's pure WDM, no KMDF dependency, no sbpcx, no acpiex)... And if you ask why I use i2cctrl.log, it's obvious, this is the only hardware with I2C that I have (it doesn't have serial port, ethernet port for debugging). On crashes I debug the crash in windbg in win11 from xp's memory.dmp (on the same hardware), while outside of BSOD through i2cctrl.log. My controller is I2C IO Cannon Lake based on LPSS, yours is I2C EC based on DW, so maybe the mechanism isn't even the same for you compared to me.
  14. Not really. You really don't have the impression on other members that your ego thinks that you do. Sorry, you just don't! Trust me on this, MULTIPLE members here do NOT like your egotistic all-knowing always-right personality. Take that as CONSTRUCTIVE CRITICISM and "adjust accordingly". Or keep replying the way you have been and REINFORCE the view that MULTIPLE members have of you. No skin off my back either way. edit: of course, having said that, I myself also RESPECT the paradigm of "I change for no man, live with it, I don't care what you think of me." so I guess you can strive for MY respect, or the respect of the MULTIPLE members that don't like the all-knowing always-right everybody-loves-to-hear-me-speak personality. again, no skin off my back either way. and trust me on this, speaking for ME and "your view of me" -- *I change for no man*
  15. @UsefulAGKHelper Still no Realtek I2S device detected. Do these drivers work and get the job done on your Asus laptop? Do they initialize devices connected via I2C?
  16. Perhaps it was the ALC262 or 268 which needed the format set before powering on the node, now I can't remember. I think it's expected for 98 FE that WDM sound drivers won't work if they are disabled and enabled again without restarting. There are some known issues with the volume control failing to appear after installing WDM audio drivers listed in old Microsoft knowledge base articles. On Windows 98 SE you may need to install the WDM Audio Update hotfixes Q242937 or Q269601, not sure if these will install on FE. If you are using Windows 98 QuickInstall these hotfixes are already included. Not sure what is causing all the "the child FDO has not set DO_POWER_PAGABLE" errors in your logs but the FDO object addresses it's listing don't match the ones logged by my driver, does this still happen without my driver loaded at all?
  17. @reboot12 https://github.com/UsefulVideos/I2C-Controller-XP/releases/tag/build-20260622-204550 Implemented support for some missing HW IDs. Also included i2cctrl_helper.cpl.
  18. @Alloyd It's expected, as SAB doesn't hook into processes in administrative context.
  19. Who’s going to take offence at that? And then get all offensive yourself, too. You really don’t need to do that. And speak only for yourself! It’s extremely presumptuous to try to speak for others. Be a man and speak for yourself! In that case, you don’t need to reply either. If you’ve no clue, it’s best to wrap oneself in modest silence.
  20. Rhetorical question. I'll not bother reading the reply.
  21. I have NO CLUE what that means. I do not have an Android device to know if those versions are new or old or how old. Shall I explain that to you in more detail?
  22. <redacted>, you egomaniac! It gets old reading your high sense of self-worth. And I know for a fact that many others on the forum think the same. I simply stated that not all of us have a MODERN DEVICE to fall back on. I could care less if you have the oldest XP computer, no one else cares either. Carry on, wayward son.
  23. BTW, the Android tablet I'm currently using is an old Lenovo Tab M10 HD, originally supplied with Android 10 and updated to Android 11. So somewhat ancient, too. But my Windows XP computer from 2000 is one of the most ancient here in the forum, I think.
  24. That's why I said "Or" as an alternative. If you don't use an Android device, you won't be able to do that, of course. Shall I explain that to you in more detail?
  1. Load more activity
×
×
  • Create New...