schwups

Member
  • Content count

    538
  • Joined

  • Last visited

Community Reputation

4 Neutral

About schwups

  • Rank
    schwups

Profile Information

  • OS
    ME
  • Country
  1. So far Version 13 is Ok. Updated on two computers (Win ME).
  2. The Driver Cleaner Pro 1.5 works.
  3. Yes, latest FlashPlayer 22 doesn't work anymore. The browser creates an error message on crash. Also a look into the ReleaseNotes might be worth.
  4. You find the chipset driver here. The bearwindows 9x driver (vbemp) for graphics could work with the integrated GMA X4500 without any kind of 3D support. The driver is tested with INTERNAL Intel G43 Graphics (GMA X4500). Another possible driver is the SCITech snap graphics driver, but probably it is untestet. The better choice is a PCIE NV 6xxx or NV7xxx or PCIE ATI up to Radeon X8xx graphics card. Don't use graphics cards with more than 256MB. Some BIOS's permit ATA/IDE configuration settings like legacy or compatible mode to run the hard disk with DMA mode (fast). If this mode doesn't exist or work, you have to purchase the R. Loew's SATA driver. Otherwise the HDD runs with very slow "DOS compatibility mode". A driver for onboard sound isn't available. Be aware there is no guarantee that 9x/ME runs on a Q43/Q45 system as desired!
  5. Probably upgrading to ME will not solve this problem. Search for Standby or Hibernate here in this forum, if the Search Box still exists since forums upgrade. You'll find a lot of topics about standby problems. Maybe you find a solution. Changing BIOS settings could help. Standby problems occur very often on 9x and ME after graphics driver installation . I always shutdown my PC's with about three clicks and standby is set to never.
  6. Hello Flasche, meanwhile PRB opened a topic about the update problem: Avast 4.8 update trouble
  7. Usually we are on uninvestigated or undocumented area with testing of programs like latest browsers with the help of KernelEX and especially Kext - Do it yourself KernelEx extensions. Mostly we need workarounds. My knowledge is rather limited to make great steps. The only currently development of KernelEX known to me is here on MSFN. A very huge thanks to jumper. I know development and testing needs very much time. How often I rebooted my computers during the past years?? I try to keep the WIKI up to date if time permits. I would be happy, if others could add more tested progams in the hope to keep the knowlege in the future, to have a place to check up. I tested unsuccessfully the Safari browser some years back with KernelEX 4.5.2 and without Kext. Tests with the rather unknown browsers were mostly unsuccessful, too, but you can give DIY Kext a shot.
  8. You can try another DVI cabel and you can give other drivers a shot (77.72, 82.16 or 82.69...). Probably you have no other graphics card to test. My monitors have a maximum resolution of only 1280x1024. Thus I have no practical experience, whether a NV driver bug could be given.
  9. Probably it doesn't make sense to to talk about a i810. This chipset has a 370 pin CPU Socket and no AGP Slot. The Pentium 4 needs a socket 478 and a Dell Dimension 4300 should have a i845 chipset. Or is it a special version? CamTron, apart from the possible RAM problem, did you check your HDD partitioning and the free space of the partitions. Do you have the WIN386.SWP file on partition C? I had freezing OpenGL programs because of low HDD space. A few hundred MB can be insufficient.
  10. Confirmation: System Win ME, KernelEX 4.5.2: Foxit Reader 5.4.5.0124: The direct copy is possible to Notepad++ or OpenOffice writer. System Win ME, KernelEX 4.5.2015.12: Foxit Reader 5.4.5.0124: Error message "Invalid User32.dll, cannot find SetLayeredWindowAttributes" Faultlog: Datum 04/13/2016 Uhrzeit 12:26 FOXIT READER verursachte einen Fehler durch eine ungültige Seite in Modul KERNEL32.DLL bei 0177:bff8e1ad. Register: EAX=c002fa54 CS=0177 EIP=bff8e1ad EFLGS=00010212 EBX=00000000 SS=017f ESP=01c3fe08 EBP=01c400a4 ECX=00000000 DS=017f ESI=01f01860 FS=3ba7 EDX=015dd8e0 ES=017f EDI=011e9cf0 GS=0000 Bytes bei CS:EIP: 53 8b 15 f4 bc fb bf 56 89 4d e4 57 89 4d dc 89 Stapelwerte: Versions 4.x: Copy function only by "text viewer" of Foxit. Apparently a copy to MS Editor or WordPad is always impossible, it doesn't matter which version I use.
  11. I am not sure what you mean. A screenshot would be helpful. Or do you mean those | in the menu? Then change the fonts to e.g. Tahoma.
  12. KernelEX will not help you to install drivers! KernelEx has the aim to run Windows 2000/XP-only applications on Microsoft Windows 98 and Microsoft Windows Millennium operating systems. Make sure you have the Microsoft Layer for Unicode version 1.1.3790.0 unicows.dll. It only needs to be inserted into the system folder.
  13. I successfully downloaded the file one hour ago and installed version 12. Win ME started without a problem. Also I ran a lot of programs without error messages. Kexbases has considerably become bigger.
  14. What's the size of the inf file and did you identify your card? The size of the drver inf file version 3.1 on linksys.com is only 32KB. That is OK. There is no need to reduce it! Shorten/reduce: Use a Editor or Wordpad program to open and edit the file. Inf files are divided into different sections. e.G.: Find the sections with the devices or components. You can delete all devices except yours. Usually Win2k, XP, Vista... specific sections aren't needed. ....
  15. I don't know the wifi card wpc54g. I searched on the support page and found this on linksys.com. There are drivers in Hardware versions 3.1 and 7.1. Version 3.1 is for Broadcom devices and contains a 9x driver. I found in the inf file of 7.1 "Atheros". AFAIK Atheros never supported ME or 9x. I don't know your version. What exact card do you have? The Tool Everest or others can identify the card. Apparently there exist different drivers for different vendors. Make sure that your card is in the inf file of your driver CD and that the size of the inf file in "D:/Driver/9x" is less than 60KB. On my ME systems it must be less than 52KB. If necessary it has to be shortened. I had the case to shorten the 9x driver inf file of a Broadcom onboard Ethernet device. Also I had experienced that a LAN driver, maybe it was this Broadcom onboard Ethernet device, was only accepted from drive C. I am not quite sure any more.