Jump to content

PassingBy

Member
  • Posts

    87
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Malaysia

Everything posted by PassingBy

  1. Hmmm ..... There's a brief explanation on RH single/multiple command scripts at : http://www.askvg.com/tutorial-all-about-re...brief-tutorial/ Rgds
  2. Hmmm ..... Sorry ya, I did post a patch but later tested it on a win95 machine and found crashboombang bug in the patch thus its withdrawn ... I have a bit of free time just now and looked at this QQ stuff again ... there's seems to be an english version out there and perhaps I'll take a look at it later ... I've found an older qq2003 that seems to install/work in win95, here : http://soft.pdsu.edu.cn/list.asp?id=681 It was a lot smaller so I d/l and made an install test run ... seems to install & start without a glitch ... don't know if you can login since I'm really dumb with chinese texts ..... I'm guessing that your old p75 notebook is a really old model that doesn't have a 2nd level cache (I've worked with those models before) thus it'll run painfully slow with win98 ... keep those linux with gui away, they'll crawl too (if the notebook is really without 2nd level cache and/or came with slow vga subsystem) ... the gui part is the one that makes it crawl ... not worth upgrading these notebooks as many old models uses proprietary ram modules ... Talking about IM, well, out of curiosity I d/l yahoo messenger 7.5 from oldversion and install it on win95osr2 ... made a quick patch and a quick test run ... seems to work on my win95 testbed ... let me know if you want it ... *Seems that I have to make a bit more adjustments to make ym 7.5 to work without error popup ... tested with ym 7.0.x up to 7.5.0.814 and all ym 7.0.x will run without modifications on win95* Rgds Edit: added text between *...*
  3. Hmmm ..... I have no idea what I'm doing with this thing ... I have never use this QQ ... let alone know what I'm dealing with ... I did this to challenge my lazy brain to see if I can make this absolutely no warranty whatsoever patch on QQ to work ... If you're willing to test, put this patched dll (make backup first) into your QQ folder and see if your QQ can run on 95OSR2... Remember, I have not the slightest idea if this will properly work ... Use at own risk ... (BTW, check that your OSR2 should have updated wsock2 and msaardk ?) QQhelperdll patch {withdrawn} Rgds Edit: out of curiosity, I installed the whole QQ thing and tried it on a win95 ... wowzer, so colorful ... but something went amiss ... somehow the patch botched something somewhere (now getting more lazy to see where) ... All other QQ apps runs except QQ IM ... sorry ...
  4. Hmmm ..... Same condition as previously, the function is not implemented on windows 98 shell32 ... It is non existent if I'm not mistaken. For that function to work, you'll need RP7 ... Rgds
  5. Hmmm ..... That function is not originally available on windows98 shell32.dll ... It's inside shfolder.dll ... The game developer may not be aware of that condition. There's two (and perhaps more) possible solution to this. The two available current options are : 1. Install KernelEx to add that function, from here (easiest method): http://www.msfn.org/board/KernelEx-v032a-r...sed-t71476.html 2. Install RP7.1, from here (major overhaul method): http://www.msfn.org/board/Revolutions-Pack...-SE-t58357.html Both have their pros and cons but will make that particular function available. If your windows version is english then there shouldn't be too much of a problem. Be advised that YMMV ... Rgds
  6. Hmmm ..... I believe what you have is windows 98 Gold/first edition. You should ensure that your updates and patches are for that particular version. Rgds
  7. Hmmm ..... Get the correct (language specific) version and it should work just fine ... Rgds
  8. Hmmm ..... Yes. The adjustments can also be made to the "new Corsair driver set" or any suitable driver set for that matter. My apologies for not having the patience to guide you through the required adjustments. Suffice to say that if you know how to identify the VID/PID (hint: it's in HKLM\ENUM\USB section) then you can proceed else better to look for a quicker alternative ... If your win98 fulfills the basic criteria for NUSB (ie. W98 FE/SE ENGLISH !) and your system's age is roughly less than 8 years old (pentium II or pentium III or Athlon) then it is a safe bet that NUSB will work just fine. The easiest and safest alternative right now for you would be to get NUSB, extract it to a folder and point windows to that folder when it detects your new corsair pendrive. This will only install the usb storage driver for your pendrive without installing the rest of the package. You can install the full NUSB package later when you're have the luxury to do so ... Rgds
  9. Hmmm ..... I've made a quick glance into your Corsair "new driver set" and saw that it is based on the MS DDK sample with very minor modifications. (In fact, most usb pendrives driver set (that I've seen) derives from the MS driver sample with almost no or little modifications ...) Therefore it does not matter what controller the Corsair drive uses ... The reason for the "New Hardware Found" wizard to appear is because the VID/PID (Vendor ID + Product ID) has yet to be registered in the device tree, hence the drivers are not loaded. If you're up to it, adding VID/PID (if it's not the same) to the .inf file will do the trick ... and ... no, these drivers are not loaded by right-clicking to install ..... I'd recommend that you use NUSB and you will no longer have to fiddle with what driver for which pendrive. Perhaps you are unaware that the NUSB driver set originated from MS (and used as a base for WinME, W2K and XP) ? So, go get your W98 specific version from here : http://www.technical-assistance.co.uk/kb/usbmsd98.php Install it (remember: follow the instructions) and enjoy ... Rgds
  10. Hmmm ..... Aladdin 5 ..... brings back fond old memories with my p5a-b ... Let me make some quick guesses here ... Iwill aladdin 5 based mboard is a super socket 7. I bet it came with either a pentium mmx or an amd k6-2 (or perhaps k6-3) or it could even be a Cyrix MII ... Depending on the onboard cache size it can be snappy upto 256MB ram ... It'll go downhill if you don't adhere to the cacheable range sizes ... Anyway, what I'm about to tell you must be taken with a pinch of salt ... There have been many reported problems with ALI usb implementation as can be found here (for example): http://www.usbman.com/Guides/ali_tips_and_tricks.htm Look for some pointers at the site above for getting Ali usb ports to work. Sometimes Ali usb ports doesn't properly work due to conflict in BIOS settings. Sometimes its plain luck (due to various bios settings differences, design, implementation, bla bla bla) ..... I've had mixed results (most are good anyway) when using win98se with ALi usb ports but YMMV ... At any rate, I would recommend reverting back to windows 98se as the ALi usb chipset is properly recognized there. It's also a much lesser burden overall for the old workhorse to handle ... To get your usb storage device to work, install NUSB which you can find in the sticky section or here : http://www.technical-assistance.co.uk/kb/usbmsd98.php Rgds
  11. Hmmm ..... Hello comrades ! I am wondering if any Delphi and Lazarus users are aware of any free standalone RichEdit component ? Most free TRichEdit enhancement are descendants of VCL ... Available alternatives can be found in JEDI (which I'm unable to use as I'm on Delphi3 and unable to afford the costly upgrades) and KOL-MCK (a favourite of mine) but their usage is bound to the respective package. There are none currently in Lazarus LCL but the one in KOL is usable but still limited to within the package (no mixing with LCL). I'm looking specifically for a standalone RichEdit wrapper component that can work with both Delphi and Lazarus. If anyone knows a nice alternative (and preferably open source), kindly point me to it ..... Rgds
  12. Hmmm ..... Seagate Barracuda IV ST340016A with 40GB capacity. The smart readings looks okay to me but as per your earlier description it does seems to have some difficulties with reading/writing. The reallocated numbers are small. There's a way to find out ... Once you have copied out your data. Use any suitable utility to zero fill the entire drive then scan the drive again. If it seems to be smooth while scanning without much stuttering then its propably safe for normal use else its prudent to use it for secondary backup. Rgds
  13. Hmmm ..... I'd like to briefly clarify a few things about the usb storage drivers issue above. From my past reading/understanding/fiddling/experimenting/blowing-things-to-bits, it does not matter what controller chipset is being used by the usb flash storage devices (Windows doesn't care about them unlike scsi/ide controllers). What matters most is the protocol that they use to 'talk' to windows. There are three primary protocols: 1. BO - Bulk only. 2. CBI - Control/Bulk/Interrupt. 3. CB - Control/Bulk. (please refer to http://www.microsoft.com/whdc/device/storage/usbfaq.mspx for more info) Most (about 99%) usb flash drives uses bulk-only and will work 'natively' on WME, W2k & above. These OS have 'native' usb storage drivers, meaning that the built-in drivers are able to support all three protocols identified and filtered by their usb storage device class-protocol or by specific VID/PID. Usb storage drivers issued by the manufacturers (if any) may have certain specific requirement. Usb fdd for example requires specific CBI support to work correctly. If a particular manufacturer driver set is a generic version (based on MS DDK sample) that supports all three protocol then it will work with any usb storage devices which uses any of the protocol. To make them work, add VID/PID of the usb device (or the usb device class & protocol filter) to the driver inf list and set the driver protocol flag. That's it ... and that's what NUSB is all about, putting together a set of native drivers with the required protocols that will work with all usb storage devices defined according to their class & protocols. There are exceptions to the above whereby the usb storage device (ie. usb-ata/external hdds) requires vendor specific 'pass-through' commands. Fortunately, these seldom occurs nowadays. There's a few other technical issues that may affect proper usage but let's not go there ... I need another vacation ... In summary, for the casual user, NUSB will be the recommended and easier alternative than figuring out the VID/PID and protocol flags. Rgds
  14. Hmmm ..... Nice ... This will be a great help to some ... Thanks
  15. Hmmm ..... Thank you for your effort and feedback ... I have made a quick check and found that the "USB Mass Storage Port" is a reference to the Cruzer drivers from Nathan's pack. That would mean traces of the previous drivers are still being used by windows. If you can/willing to give it another shot, here's what you can do. Remove all references to the cruzer drivers by deleting all refences to SND95*.inf in windows\inf\others. Search and remove all instances of USBIMW95.sys and USBSTW95.pdr. Remove instances of the usb sticks from the registry or hardware control panel. Reboot first to clear any loaded driver for the usb devices. Then try out the usb storage drivers. If windows requires a reboot after detection then it can mean one of two below : 1. Driver conflict/mismatch. 2. Device using unsupported/specific protocol (CB/CBI/Authentication etc etc). (* I'm still looking for suitable drivers for these protocols.) I have also made changes to the ejectusb utility above. Please use the updated version instead. Rgds
  16. Hmmm ..... Sounds like surface degradation or mechanical defect(s) to me ... Probably more prudent to not run another scandisk at this point. If the scan stutters all over the drive surface, it is possible that the read/write section (maybe amplifier/coil/etc etc) is wearing out. IMHO, you should attempt to copy your most important documents first before running a scandisk again. If the previous scandisk has gone through the first 10%-20% of your drive, it "probably" has fixed the FAT and DIR (YMMV). After having copied those wanted documents then you can attempt to scan the drive again. If the drive is a slim maxtor, its going to RIP soon. If its a seagate, data recovery is possible but will burn a big hole. If its a WD, a surface erase can be of some help. If its a Samsung, its odd coz they're tough. Rgds
  17. Hmmm ..... I've just patched OpenOffice 2.3.1 (sal3.dll) to run on windows 95 ... Its still the same IsDebuggerPresent patch ... No problems so far ... If anyone wants it, kindly let me know ... Rgds
  18. Hmmm ..... Where it is placed & how to remove: 1. The driver pack will add usbstor.inf and patched nodriver.inf to the INF directory. 2. Storage drivers will be copied to OPTIONS\CABS directory. 3. The device removal utility will be placed into SYSTEM directory and a startup ejectusb link will be placed into HKLM\Software\Microsoft\Windows\CurrentVersion\Run 4. Device class ID will be added to the registry. 5. To remove from using the drivers again, delete usbstor.inf from the INF directory. 6. Remove ejectusb startup link as in #3. 7. To remove usbstor driver usage comletely, remove all references to the required VID/PID under USB and all in USBSTOR in the HKLM\ENUM\USB registry section. Do not remove ROOT_HUB entries. Those are for usb root hubs. 8. Remove all driver files as listed in the _usbtor.inf The eject/removal utility does not write anything to the registry. It is a beta version systray utility with a close/exit option. It will only show usb devices if it is active, else the list is empty. Rgds
  19. Here's the systray usb storage removal utility works on all Windows 9X... Please make some test runs and report any issues ... *Note: For windows 95, double-click on the .reg file to add Device Class GUID Rgds * Updates 26-DEC-2007 * - Major changes to source code to primarily use cfgmgr32 routines. - Workaround an issue of intermittent setupapi failure on win95. It does not occur on win98 and above. - Workaround an issue with excessive memory usage. Only occurs on win95 due to how setupapi is managed by windows. * Updates 5-JAN-2008 * - Bugfix: library unload sequence corrected. - Excessive memory usage solved. EJECTUSB.RAR (0103-for historical record - DO NOT USE) EJECTUSB.rar EJECTUSB.RAR (0108-for historical record - stable with dll unload bug) EjectUSB_0108.rar EJECTUSB.RAR (0108b - latest stable with bugfix) EjectUSB_0108b.rar
  20. Hmmm ..... I have been working (on-and-off) on usb storage driver pack for windows 95B/C ... It is currently only half complete and has quite a bit more work to get it completed. Nevertheless, it is a working pack. I am requesting windows 95 testers who wishes to try out this pack to provide feedback and help me improve it. The drivers itself was collected from the web and tested for suitability & compatibility. The current driver files has been modified to point to USBSTOR in registry. I am attaching the systray usb removal utility on the next thread for testing on win9x platform. It is intended for windows 95 but has been tested to work on all win9x system. On windows 95, specific device class ID (usb,diskdrive,cdrom) needs to be added to the registry for it to work (included with the utility). Please report any issues with it. Rgds USBSTR95.EXE : Usb storage driver pack for windows 95 (Beta 1) USBSTR95.exe
  21. Hmmm ..... Thank you for the archive. Could you kindly place 'em on multiple sites please in the future ? The ones on rshare is taking me nearly 10 mins just to get 2.4mb ... Rgds
  22. Hmmm ..... Impressive ..... Most impressive ..... Any chance for us to apply it to our system ? Rgds
  23. Hmmm ..... Nusb98fe versions have been corrected since 3.12 ... can anyone confirm whether it should be ENG or ENU ? or something else ? or its a minor thing ? Rgds
  24. Hmmm ..... IMO, the above statements are correct ... I presumed that when the (old) scanners came about there was no usb 2.0 support working properly on windows 98. To get proper usb 2.0 working requires correct drivers to be installed. There's currently two ways that I know of to install usb 2.0 drivers for windows 98. First would be through chipset vendor drivers. Second is by installing NUSB. Current usb 2.0 drivers can work on both windows 98 gold (may require minor patch) and second edition (natively). Once usb 2.0 drivers are installed and working then most (if not all) usb devices can detect and use the required usb speed (if at all). Rgds
  25. Hmmm ..... Socket7 and SuperSocket7 performance is tightly related to chipset support. Most S7 can only cache memory upto 128MB/256MB. Some VIA S7 can cache upto 512MB or even 1024MB. Even with k6-2+/k6-3+, the chipset still have a role to play. I did have an experience with k6-2+ 500 on an VIA board 1mb L2 cache with 512MB RAM a long time ago. It was lightning fast (at the time). Disable that L2 cache, and things start to go a bit slower ... In contrast, a SiS S7 chipset with any S7 cpu is limited to 128MB cacheable range (most model). Go any higher and windows will crawl ... Rgds
×
×
  • Create New...