Jump to content

dencorso

Patron
  • Posts

    9,129
  • Joined

  • Days Won

    63
  • Donations

    25.00 USD 
  • Country

    Brazil

Everything posted by dencorso

  1. Still interested. I'm interested, too. Please, by all means do post detailed instructions... they may be of help for many.
  2. There's no other link, sorry1 But the one I gave you is working OK for me, I've just tested it. In any case, here's the direct download link (from that page you aren't being able to reach) ATM v.1. The Wayback Machine can reach back straight to 1996! Unfortunately, as of late, they began honoring robots.txt retroactively, so when the site still exists and they decide to prohibit crawling, all previously cached content is deleted from the Internet Archive (or, at least, stored beyond reach, but I doubt it: space is a precious commodity for them, so deleting, which is what they say they do, makes more sense, in that context)... and this has resulted in the definitive loss of access to numerous pages related to 9x/ME that have been retired by MS (and were still reachable through the Wayback Machine for a while). In any case, access to the Wayback Machine is somewhat erratic at best, so when you cannot connect to them in the 1st attempt, do try again later, for odds are sooner ort later you'll succeed.
  3. I guess you might like the good old ATM, by Tim Murgent. This link I provided takes you to a Wayback Machine archived page you can download the old version 1 from, and that's important because v. 2 and v. 3 don't run on XP. ATM is not a program to use as an always on monitor program, but is convenient when you want very detailed information. And thanks for the links you've provided!
  4. dencorso

    sp3.4

    Yes.
  5. While I don't find time to add such a feature, there's a good workaround for it (warning: NT-family OSes only, sorry... the for command in 9x/ME does not do it). Try: For /R "C:\Program Files" %1 in (*.*) do vrfype "%1" | find /v /i "dencorso" >> D:\TEMP\vrf2test.txt ...and you'll see it traversing all subdirectories of "C:\Program Files"... of course, if you use "C:\" it'll do it over the whole C: drive. Now, "D:\TEMP\" must exist before issuing the above command, but vrf2test.txt need not: if it does not exist, it'll be created. vrf2test.txt will contain a blank line for each file tested, and a blank line plus a line containing the fully qualified name of the file for those files having non-matching checksums... Of course, that's too many blank lines. But you can remove them using my yanklines script: yanklines vrf2test.txt vrf2clean.txt ... if run from the folder vrf2test.txt is inside... or from anywhere, if using fully qualified filenames. Or you can get any of the many DOS or Win32 sed ports, maybe also with the companion unix2dos port for correcting for the different unix and DOS end-line conventions, and run: sed "/^$/d" < vrf2test.txt | unix2dos -D > vrf2new.txt ...bear in mind some sed ports require double quotation marks <"> while others prefer single quotation marks <'> for containing sed regular expressions. Both alternatives produce almost the same result, but that sed command will remove all blank lines, while yanklines will let a single blank line remain (because it was created to remove duplicate or multiplicate lines). Of course, all this can also be automated in a .cmd script.
  6. In any case, the best replacemeny for the name "Metro" ought to be the prophetic "Fail'll" or "Failwill", or even "Fail-0"...
  7. While the partition table in the extended partition has four slots, just like in the MBR, the logical partitions inside the extended partition are connected in a daisy-chain, which means only one ot two of the slots are ever used.
  8. Fixed! It's interesting to notice that windows saw 3583 MiB with the ATI Radeon X850 with 256 MiB VRAM video card, but on moving on to a XFX nVidia GeForce 7950GT AGP with 512 MiB VRAM video card (so 256 MiB more) windows started to see 3071 MiB (which is precisely 512 MiB less, twice the VRAM amount added). Then again, the comparison is not perfect because the original video card was an ATI, while the new one is an nVidia...
  9. Fixed! Both are good guesses. I'd bet on different boards, different maximum possible specs... but Win ME *is* quite different at the lowest level from 98SE, possibly enough to allow such different results, too.
  10. For some reason, this crashes with my sata drive.We need a better solution. Maybe this can be fix with some patching etc...... Do please try the Paragon solution, which is apparently the simplest alternative, before going on to more complex solutions.
  11. I'm using both wuweb.dll and muweb.dll v. 257, without any issues, to this day...
  12. This topic has been updated! What's New? on post #2: Dave-H's, TmEE's #3 and LoneCrusader's #2 machines configurations have been updated. Let's keep the list up-to-date: If you are using 9x/ME with more than 1 GiB RAM, do PM me your info and you shall be added to the list!
  13. Well, in any case, that's a Russian site, so Tihiy is better equipped than most of us to complain there. But, in any case, with threads about it here, and over in Neowin and MDL, all linking Tihiy to this product in particular, that "mustdie" must be out of his mind if he thinks he can get away with pretending to be the developer! Later edit: I don't think "mustdie" is trying to claim authorship, really. I just noticed that just above the download link, there is a lone word: "Источник" that, according to Bing Translator means "Source", and if one hovers the mouse pointer above it, it's a link to the MDL thread. So I think he's just trying to spread the word. Of course Tihiy can complain about unauthorized redistribution... but I do not think he will.
  14. Happy Birthday PROBLEMCHYLD!
  15. This topic has been updated! What's New? on post #2: LoneCrusader's #1 machine has been updated, and his new #2 machine has been added. Let's keep the list up-to-date: If you are using 9x/ME with more than 1 GiB RAM, do PM me your info and you shall be added to the list!
  16. If I had to hazard a guess, mine would be "ASCII" and "Unicode"...
  17. Well, this being the case, I think RLoew's suggestion is the best thing to try next.
  18. +1 Whatever I ever write, bear in mind that I respect deeply you yourself and all the hard work you've put into this project... you've breathed new life into the uSP, at the time it was most needed. And I do appreciate your effort to accommodate as many people as possible, too. So, of course, that could not possibly be what I meant, no matter how strange my post may have seemed... I'm glad we're now everybody on the same page again.
  19. Thank you, Multibooter, for testing VRFYPE! The previous version had just the help switches, but the new one has some new ones. "a" gives an output similar, although, I hope, more meaningful and shorter than the one produced by the original version. Here are the contents of the help screen: Usage: VrfyPE <filespec> </option> where: ? or h = this help; 0 or z = checksum not set only; g = matching checksums only; a = all files with checksums; non-matching checksums is the default; Fully zeroed files do not have the PE headers, so they are ignored as non-PE files. PE files with block of zeroes below the headers will be duly flagged as having bad checksums... So it's important to look each of the flagged files to find out why does it have a bad checksum. One of the things I always do is to submit them to VirusTotal. And there surely are some files the publishers release with bad checksums... two cases-in-point are: QuickTime.cpl (v. 7.66.71.0) => Cheksums: Header = 0013644A Real = 001840F0 (a bona-fide file from Apple) mpg4c32.dll => VirusTotal Report (please scroll down and click on "Additional Information": it is indeed a bona-fide file from MS)
  20. Another possibility: check whether you have a NoSaveSettings with value 1 under each of the following registry keys... HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer HKEY_USERS\.Default\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Program Manager\Restrictions HKEY_USERS\.Default\Software\Microsoft\Windows NT\CurrentVersion\Program Manager\Restrictions HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer If you do, change that value from 1 to 0.
  21. @RLoew: With all due respect, I do disagree: RetroOS found at least one case in which the Win XP USBCCGP.SYS is required, because USBHUB.SYS does not cater for many USB composite devices. The problem here is related to KVM devices, and perhaps some others, too. That said, I must add that while I'm a satisfied customer of your WDMEX.VxD, which has more functionality and, being actively developed, can add still more, NUSB's needs, up to now, have been adequately satisfied by WDMSTUB.SYS, which is also a 3rd party file. I do however reckon WDMEX.VxD will be fundamental in the Bluetooth/USB 3.0 quest, and that's why I became so happy when you started its development.
  22. No I did not say that. I think adding files from ME and 2k very useful. Most of the progress that has been done, has been done by adding files precisely from this origin. I did contribute myself to the adaptation of some of those files, as you fully know. So I cannot be saying that. What I said is, it's much more difficult to do it with XP files, particularly so at SP3 level, since we then are much farther from 98SE then. But RetroOS did so with success with USBCCGP.SYS, and I am one of the few that long advocated using the 32-bit twain files from XP SP3 in 98SE. Both these cases work well. BUT files which deal with OHCI and UHCI, that is the USB 1.x protocol, should add nothing new to 98SE, since it has that functionality already, and its USB 1.x protocol is bugless, AFAIK. Moreover the USB stack model changed from 2k to XP, and that can be seen easily because there's no USBHUB20.SYS in XP, all that functionality having been retrofitted into its USBHUB.SYS. So, with all due respect, I do think there's too little room for improvement in 98SE's USB 1.x stack, while Bluetooth and USB 3.0 support are unexistent. And, if we ever get to make those things work in 98SE it must be using either XP or 3rd party files, because neither ME nor 2k have any support for them, too. This is what I meant, and I sure didn't mean no disrespect, in no way.
  23. Transplanting XP's USB stack to 9x/ME is a loosing game. There's nothing to be gained, in what regards functionality, and plenty to be lost. RetroOS's success with USBCCGP.SYS is a rare exception, and there there was a problem to be solved (and solve it he did). Also getting XP's USB 3.0 to work on 9x/ME is a worthy quest. But simply upgrading to XP's file for things that already work well with the currently known drivers, with all due respect, seems pointless to me.
  24. You have two options: Ext2Fsd or Ex2IFS, so read about them and take your pick. I know they're able to mount normal ext2 partitions, but I cannot guarantee either will mount a linux ext2 ram disk image. Do not forget to create a full system back-up, before you install either, so that you can recover easily, if anything goes wrong.
×
×
  • Create New...