• Content count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About go98

Profile Information

  • OS
    none specified
  1. Right, not always easy to make a good and clear presentation, I tried to make it clearer now...and thanks, Problemchyld, for the picture
  2. If you create a shortcut on the desktop using this method: right-click a file in explorer or on the start menu -> Send to -> Desktop (create shortcut), there's another of those unnecessary dialogs that pops up every time. If you want to get rid of that, you can hexedit shell32.dll at: search for the bytes 6A 40 68 37 10 00 00 68 14, then change the first two bytes to EB 1B (I have 98 SE, but other versions may have the same dialog and fix). Note: the SendTo target is Send to (separate words) in my language version.
  3. Well, I don't have this problem, I tried to push it with screen savers and the program ACDSee (v2.1)...(btw, nice tiny program, Jumper!). Do you all use a heavily fixed explorer.exe for the english version? So, what are the other 49 flaws...? Or 48, you just posted another one.
  4. Drugwash, I always wondered if you were a former drug addict, but not so... Apart from that, I started with windows 95 at home, then 98, and later 98 SE...and kept it until around 2008 when I bought a new computer which ended up with windows 7 hmmm...until I saw this forum, and got back the hope...alone with little time, there's not much you can do, and I never even thought of fixing the OS myself before. That's all changed now Well, I always liked the BIOS too...sadly, it had to be replaced
  5. I had wished you would say: "Unless it's a *really new* PC, I prefer Win98SE..."
  6. Ha ha, Dencorso, you've been around for some time to have found out that...thanks for the tip, I will have a look, maybe it can complement my own tool...anything that can further simplify the task is good. However, it was partly because of IDA I decided to make my own disassembler, I wasn't satisfied with how it works (at least the free version). Jaclaz, thanks for the quicker-than-upstart-of-windows-7 response
  7. Anyone knows of any good downloadable vxd disassembler? I never saw one, had to make my own...vxd is not strictly LE format.
  8. Hmm, CamTron, I insist, this is an interesting problem, but hard to diagnose if it's not clear how...or...when it is hard to diagnose, suspect the hardware... Acctually, it's a better starting check-point to do according to my instructions than using the setting you mentioned, because then we are down in the vmm/vxd-line directly. For those who like it technical, it's controlled by the locked code section in reboot.vxd, but it's also calling services...where does the locking possibly occur? => interesting! In the end, if ppl in this forum together get it rock-stable in the future, you might even transform into an 9Xocalypse survivor
  9. That's great, rloew, at least one dedicated 9x-developer who can work full time (I assume) on solutions...
  10. Well, your just-for-the-record links are not just for the record, they are actually quite good
  11. Are you runnnig windows 98 on more than one core? Seems you are in for a 9x version of ReactOS...haha, no not that...better with the real thing, though modified...
  12. Hello, yes this is interesting. The problem is, that to find the cause, it has to be reproducable in an exact way. ...but if you experience this often enough, you can assist by doing this: The file kernel32.dll (c:\windows\system), which you cannot alter directly, but need to make a copy first. If you know about hex-editors, then search for the following bytes (there's only one occurance): 6830A0F7BF Now, go back 5 bytes in the file where the byte is 55 and from there enter the following: 6A006A01FF152CB3FCBF When finished, exit to dos and replace the original file with the one you changed (keep the original file too). Now, everytime you press ctrl-alt-delete, the computer will shut down immedeately. This way we will get an idea of where to start...because there are 2 possibilities, either it works or not when your computer locks/freezes and so we can rule out things. My time is limited, so I may not be here too often, but sooner or later things get fixed by someone... NOTE! It's always risky to edit important files, so you decide! I only see my own system.
  13. ...just to keep this forum more liveful... and show the NT-guys this is where the action is haha There's a small glitch in the tray volume that shows like this: In the tray area, click the speaker icon once to get the volume window appear, then click elsewhere and the window disappears. Now click again on the speaker icon...this time you can't get rid of the window until you have clicked in the window first... Here's how to fix it: In the file sndvol32.exe (in the windows folder), you need to hex edit the following: At address (offset) 1D48: 6A 00 change to 90 90 At address (offset) 1D4D: B8 change to 3C For other languages which may have different locations: Find the first occurance of this series of bytes: 56 6A 08 8B 74 24 0C 56 That would be found at address 1D2D in my localized version of the file. Now you can calculate the distance yourself to the above fixes. However, it's possible that the second change from B8 to 3C is not found, so technically what has to be done is changing a call address from ShowWindow to DestroyWindow (user32 functions) while blanking out one unnecessary parameter.
  14. Thanks for the clarification...and welcome back to this forum again after a long holiday, Problemchyld
  15. If I may add my three cents in, I´d go directly the cab-way...I have patched the relevant files in the cabinet and so have it set already on install...and never have to think about this anymore...I am sure if you talk to Rloew, he could assist you doing it this way, if you want it more convinient.