Jump to content

Ninho

Member
  • Posts

    186
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    France

Everything posted by Ninho

  1. Do the replacement from another OS instance, or disable system file protection (lookup google for how to do that. You'll need to change one registry value *and* in addition hack two bytes in sfc.dll if I remember well). HTH -- Ninho
  2. While launching Windows from the original CD for repairs or installation : is there a way to specify a plain IDE disk controller (not SCSI, RAId or anything fancier...) in replacement for the ones built-in (atapi.sys, intelide.sys, pciide.sys, pciidex.sys, etc.) ? One good reason to do that would be the bug described in Microsoft's KB article 254769. Oh, wait ! MS was so ashamed it *removed* the article from its servers! Webarchive is our friend : <http://web.archive.org/web/20030212214431/http://support.microsoft.com/?kbid=254769> So, please... how can we build a driver diskette including a substitute intelide.sys (for instance) and have it loaded by Windows using the [F6] procedure ? How would we write the appropriate TXTSETUP.OEM - along with any other required files ? -- Ninho
  3. A quick and dirty way would be to look inside %windir%\system.ini (text file) : scan the [boot] section for a line similar to : oemfonts.fon=vga850.fon This example is telling that Windows was installed using OEM CP 850. CP437 (EN/US) would use vgaoem.fon, others use vgaxxx.fon where xxx is code page number. This is a good guess, not 100% foolproof, for the oemfonts could have been changed by someone or something without affecting the CP used for DOS filenames... Should you find discrepancies, there is (used to be) a utility on the Win 95 installation CD which supposedly could change CPs after the fact, unsupported and with all the caveats. The version from Win 95 does NOT work properly on Windows 98, and I don't know if there is an updated version on MS Windows 98 CDs - it is definitely not on my Windows 98 OEM preinstalled :=( That whole internationalisation affair has been a total fiasco ever since the days of MS DOS 3.2/3.3, when MS started to take over the lucrative business of selling DOS to final users; previously they had been licensing DOS to OEMs who would do the necessary local adaptations themselves. I'll do some testing later...
  4. Welcome to i18n - internationali{z|s}ation hell ! The differences you noticed might be related to the following general remarks. Under WinDOS (Win9x/ME) what characters are allowed in filenames, how they are processed and stored will vary depending on the code page as set in : - CONFIG.SYS : COUNTRY= ... That should be consistent with the "codepage" which was selected [probably, by default] at the time Windows was installed (this cannot be changed later, at least not easily and reliably, certainly not in any way sanctioned by MS). If you do *not* have a DOS 'COUNTRY=' statement, or no CONFIG.SYS at all, then defaults apply - generally language settings of the USA and CP 437, but really the defaults are built-in to IO.SYS and some regional versions of Windows might vary. When booting to Windows 9x safe(?) mode or command-prompt-only-safe(?)-mode, as might be useful precisely when trying to repair the kind of problmes with file names, your CONFIG.SYS if it exists is bypassed anyway : another possible source of puzzling problems ;=) In addition, if multibooting with an NT-derivative such as Win 2k, XP or later... the way those later systems store "legacy" 8.3 aliases on FAT(32) systems is subtly different from the way it is done in Win 98 and similar, which will lead to Scandisk complaints. There are additional complications with some DOS and Windows versions that try to accomodate double-byte character sets. Microsoft never managed to deal properly with i18n, Unicode support in later OSes made it slightly better but created new conflicts with legacy systems. HTH -- Ninho
  5. I have 2.2 build 2129, the last one working under Windows 9x - I remember I had contacted Foxit and contrary to the OP, was lucky enough to be served by a competent person who even sent me a download link while the version was no more accessible from their regular web pages. This version not only works well on 98, but is shared with Windows 2000 on which it works equally well - without reinstallation or duplication.
  6. Interesting subject... I also have a similar mystery key, which iwon't paste here in case it could be revealing something which ought to stay secret (haha! I'm the most paranoïd in this thread!) Had worried about it some time ago, but could not find anything related. I think it appeared after doing some windozupdate, it has to be a MS thing. Oh, and it's Windows 98 SE, 128 bit crypto, French.
  7. In the "stickied" Last Versions for Win 9x... Herbalist recommended the program, Test-Run v_2.1.2 . I had a look at the author's archived website, but after reading the help page I still have a question I'm not clear about : does Test-Run work on Windows 98 systems with multiple users ? It says on the help page that Test-Run stores its copies of user.dat under the WinDir, which makes me suspicious that the program predates the introduction of multiple log on accounts by MS (was it along with IE 4 ?). That would make the program much less desirable of course. I haven't downloaded Test-Run pending your gracious answer; Herbalist, or someone having experience with that program ?
  8. Kerio 2.1.x of course! Never a problem on Win 9x (nor on Windows 2000). Analada : I concur, grc's Shield's Up! is a good resource for testing firewall settings, and generally http://www.grc.com is an interesting place to visit and peek around... cheers,
  9. Utter cr@p!\\\\\\\\\\ (politically correct version : use of that product may require a certain amount of caution.) $0.00 is overpriced, it's not worth the download IMVHO. In my experience : - did not identify ANY partitions - not just NTFS ones - on an external USB disk, which however were perfectly mounted and accessible, by letters, in Windows. I gave Paragon NTFS the benefit of doubt and retried twice, wensuring the USB disk was plugged in to the system before rebooting the machine. Still no joy. - on the main (fixed) disk : failed to create a new NTFS inside of an extended partition, or - actually - it created one but failed to properly chain it to the parent EMBR. - generally PNTFS conflicts with Vadim Burtyanski's excellent Letter Assigner, a must if you ask me. - last but not least, while evaluating PNTFS, it crashed Windows 98 SE. I wouldn't dare use PNTFS to /read/ an existing NTFS part if by chance it succeeded to recognise it, even less so try to /write/ ! Needless to say that thing was removed from my system in less time than it took to install. Good riddance. If someone /needs/ to access NTFS partitions from Windows 9x, there are other solutions - formerly from Sysinternals' Russinovitch - that actually /work/ Just my 2 cts -- Ninho
  10. Hmm, thank you. I have an old Norton Desktop for Windows (16 bits!) somewhere, could do similar stuff I bet. I'm rather after a specialised executable program (not a general macro interpreter) that will enumerate windows on the user desktop, apply required actions, and bail out. Like cmdow does in NT. Any such beast ? -- Ninho
  11. Hi, guys and gals ! I'm looking for a light command line program for use in batches, that will hide or close or minimise, etc, individual windows selected by (part of) their titles (or window class, etc.). On NT derivatives, I use "cmdow.exe" ; can you advise one for use on Windows 95/98/ME ? Should be a freeware/postcardware. Cheers
  12. Impossible to diagnose such things with so vague information and without access to the affected system, as you understand, besides I guess you're at least as qualified as I or anybody. All I've been trying was to suggest leads you could follow, in particular ACPI may be a factor, or not. I would go on trying to chase errant VxDs, using a trial-and-error approach. Good luck !
  13. So you nailed it down... You /might/ be able to unload the reluctant vxd "by hand", or rather using some dedicated dynamic-vxd-management app. Caution ! (added) If Fiolog is the one thing that bugs you, change the defragmenter's settings so it does not "optimize programs so they start faster". Then check running processes for "taskmon.exe" : you do NOT want to have it in the list. Perso I have never found it to be any worth in lettin the defragmenter monitor the programs' starting phase. YMMV. (/added) This last part is easy to answer : power down uses ACPI (unless on very old mobos which used APM), rebooting does not need it. ACPI is a mess which does not always work correctly (since it was invented and imposed on the industry by the devious brains at M...soft). Cheers
  14. My 2 cts : issues of the kind are likely caused by virtual device drivers (vxd) manageing incorrectly, or not at all, the messages that VMM broadcasts to all vxds before allowing Windows to shut itself down. Check those offending applications for them having dynamically loaded VxDs. You can use a GUI tool named "vxdview" ; in fact I know of two different such tools going by the same name, either will do. If it is in fact an inadequate VxD hanging your OS at shutdown, I'm afraid you can't do much anything save for finding an updated version of the app or its vxd, or stop using the app, else live with the inconvenience. -- Ninho
  15. Hi Win2000 ..! Using your system, is it possible to install and run Microsoft "vhdmount.exe" utility under Win 2k ? Vhdmount is part of Virtual Server 2005 but can be installed without the bulk of virtual server, under win XP. The installer won't run under vanilla 2k, and the exe, when transported from a working XP installation, doesn't run - complains about missing functions in dependencies. Did someone try and succeed to install vhdmount under our beloved Windows 2000 ? Or is it a no,no ? Respects, -- Ninho
  16. You don't appear to have a "double context menu", but you do have duplicate or otherwise superfluous entries. Some of those might be registered under your account while the ones doing double duty are under "all users". Please browse, review and clean-up useless start menu entries using explorer...
  17. Just tried this. Unfortunately on my system, it will boot Windows in fallback video mode (640*480*16 colors), with a message saying the videocard couldn't be configured; and even though windoze offers to change the display mode, it will /force reboot/ after doing so : upon reboot, go back to square one ! This goes to prove that the DOS part of config manager may be useful on some systems... I'll still keep Tihyi's reduced IO.SYS, will be great for booting DOS 7 from floppys. -- Ninho
  18. Oh, I see, sorry again : I'll have to try and doctor that picture by myself then. Case closed. -- Ninho
  19. Ah, good thing then. Apologies for being so dense, that bitmapped image doesn't seem to come with Win 2k Pro. Where then am I supposed to be able to download it from ? MS websites are so vast and hopelessly unbrowsable for content where you don't have a download URL :=(
  20. Damian, I've been wondering if it would be possible to download the original bitmap (desktop background) WITHOUT the "Windows 2000 Professional" (or any other) logo ? I love the image and would like to use it on a windows 98 box I'm rebuilding for my wife. I suppose one could remove or blurr the logo by doctoring the image somehow in a painting program, but I'm really nothing close to an artist, no more so with electronic brushes ! The image is needed for personal use on my computer(s). Would there be copyright problems ? Regards...
  21. You're welcome Damian. The solution for me was to restore files, uninstall pack and then reinstall it from a non volatile location. However even after that, I have uninstalled again 'cause for some reason several of the file patches do not succeed on my system whatever and I don't want it badly enough to take the time to debug this. I have seen enough of it that I can say, nice job ! I'll remember to try the next version, for sure, and oh! I have kept the nice screen background image. Can we download the original image, without the MS Windows logo and version ? -- Ninho
  22. Yes indeed. I couldn't imagine the installer would memorise it being run from the Ramdisk and try to run something from there after a reboot. Admittedly /I/ was shortsighted, let's say fifty-fifty ;=) I had noticed that runonce thing and deleted it using regedit, do you recreate it on occasions ? But why do you insist on running the refresher from that temporary path instead of where the software is installed ? Alright I guess you now have enough information to help me clear the issue. Thanks again !
  23. Greetings, Damian666 ! Trying Vistapack on Win 2k SP4. Having a problem :=( unfortunately, on every reboot, windows wants to run R:\TEMP\refresher.exe and fails (because R: is a ramdisk, duh). I guess the refresher in question would be the one under : D:\PROGRAMS\Vistapack 2000\Tools, but... why does the system keep looking for it on R:\TEMP (I couldn't find a registry entry or inifile with that reference in it !) ? And more importantly, how do I change it to fetching the refresher from the right location, assuming it is needed at all of course ? Thank you very much
  24. Hullo there WildBill !... I have a few remarks\\\\questions : 1- This is /not/ intended for CRT monitors, right ? I mean, subpixel antialiasing is what this does ? 2- The configure... option opens a box with copyright info; no configuration options on my system. Is this intended, for later enhancements maybe ? Tried it nonetheless on my CRT. 3- subjectively it doesn't make the fonts better looking in Firefox. Does add some strange effects :=) In console fonts, letter "k" disappears out entirely :=( I guess smoothtext is not for me at the moment. If any of this is of use to you, so much the better ! Cheers -- Ninho
  25. +1 ! Care to share your experience by writing down a 'how-to' and posting to this forum ? That would be very nice ! I for one haven't jumped in yet for the reason you stated above, confusing-looking instructions on the Japanese site, compounded with the fact that I have a non-English (and non-Japanese!) version of Windows. It sure would help me and, I bet, many others, to look-up better worded English instructions. And if Win2000 (praise to him) became interested, you might eventually arrange to have your international instructions added to his site too. Just a dream...
×
×
  • Create New...