Drugwash

Sure , just kidding , though of course it might have been affected by the malware in 2008, before you did burn it to CD/DVD, for all you know. jaclaz I know you're kidding. And you got a valid point, as a file can always get corrupted even while being downloaded, not to mention by any malware active sometime between download and burn. That's why it's best for us to be as precise as possible when dealing with files. I wonder if there's something else to this installation, such as a control panel or a place to enter that registration key or whatever it's called... I never got around installing and testing this package so I'm virtually interested in the matter, should I ever need to.

Sure, the storage media may not be relevant per se, it just offers credibility in regard to any possible malware attempts at modifying it, if it were on a write-enabled medium such as a HDD. Just in case anyone wanted that particular file, would it have been different from what is available on site. (thanks, den. it's OK. I'm slow, my connection is slow, notifications are delayed. this reply is superfluous now. and I need better glasses)

For what it's worth: the version of Paragon NTFS for Windows 98 I got directly from them sometime in 2008 is a single executable file (some kind of installer or self-extracting), sized 2034 kB and dated December 18, 2003. That file, along with a so-called license I've typed down to a text file, are on a DVD of mine burnt December 22, 2008.

What I usually do: - search, grab and read the motherboard manual to find out CPU/RAM/HDD/etc specs and make sure hardware fits the specs - search, grab and unpack drivers for the specific hardware installed in the target machine, right on its HDD, if possible on another partition (requires access to that HDD, either by booting a live Linux CD/USB or mounting the HDD on another computer) - copy Windows setup files on target machine's HDD, if possible on another partition (see above) - start windows installation from CD (or floppy if BIOS can't run CD/USB boot) - if during installation the Windows CD is required and setup can't "see" the CD (because CD drivers are not loaded at that time), just point the installation to the Windows setup folder on the HDD - if other specific drivers are required, point the installation to the specific driver folder on the HDD Certain drivers come as a self-extracting executable file, so you may skip installation of such driver during Windows setup and install that driver at a later time, when Windows finished installing. If you can't get access to the target machine's HDD prior to installing Windows, then try to build yourself a Windows bootable CD that contains USB drivers (NUSB by Maximus-Decim would be a good choice), install those drivers when Windows finished installing and then you can copy over the required drivers through an USB stick or external USB drive and install them when Windows is installed and running. Good luck!

I have a MSI GeForce4 Ti4200 AGP8x in my 98SE machine. The fan indeed broke and I had to replace it. However, it has major problems with generic nVidia drivers: AGP texture gets disabled. It only works with proprietary MSI drivers which are very, very old. And even using those drivers there are problems with 32bit icons not being transparent under Revolutions Pack in certain apps. I also have a 5700/128MB RAM on an XP system and it performs rather poorly. I'd go for a 6600/6800 card anytime, but got no money for it nor the ability to reach eBay. As dencorso said, card's slot key(s) should be the best indication. But please be aware certain motherboards may have poorly designed AGP slots with no key so make sure you don't mix up card's key(s) or you could fry it right away.

In regard to the future, everything goes. Maybe we can't grasp the "bigger plan". Maybe it's all as it should be. Or maybe not. However, I must apologyze for hijacking this thread with a completely off-topic discussion. My friends, please let's stay on topic. And please do not capitalize that w in my nickname - there are no such implications intended. Thank you!

Well, let's not imply anything, shall we? I'll PM you these days, as soon as I get a few things off my mind. It's quite a busy time of the year...

In regard to those OS versions, an educated opinion should be offered by people that have intensively used them and/or analyzed their behavior. Personally I never had the chance to use NT or 2000 and the period I had a ME setup was quite short because that respective HDD died quite soon. So I can only speculate. I like that - prove me wrong, people. I know you're teasing me and it's OK because I do have a healthy sense of humor. A serious and argumented talk might not be appropriate for this board. We can do that in a really free place or a peer-to-peer talk. I'd like to revive my long-forgotten Italian.

The NT-based systems are far more vulnerable. But since they are mostly if not exclusively used in business environments, I figure there may also be other ways to get to them. Win9x has usually been (and probably is) used in home environments, harder to reach individually. Don't take this for granted - I'm a huge sci-fi fan and a known paranoid. Nevermind my paranoia gets backed up every once in a while by facts...

Here's the deal: Microsoft wants Windows9x dead because they (and others along this chain) cannot control such machines remotely. Developers are somehow being blackmailed to drop Win9x support for that so-much-desired "windows logo" attribute. They wanna sell their stuff so they'll immediately drop any kind of 9x support in their applications just to get MS' clearance. For many developers, "Windows" compatibility means whatever range of OS versions is still officially supported by MS. That's the easier approach, especially where those applications are cross-platform so there's also Linux, Mac, etc versions available. Some developers who have little to no contact to "second-hand" world have no idea there still are many Win9x users around the world, for whatever reason. They would drop 9x support just for convenience or due to hardware/software upgrade, where VC6 or similar would be unsupported. In limited situations, when contacted, they would respond positively to Win9x compatibility requests. Progress has knocked down the door and we're caught in a corner. This is not a 'live and let live' world. We do whatever we can to survive...

1. That shortcircuit might have irreversibly affected the board - keep that in mind 2. Get yourself a multimeter/voltmeter and check all voltages at the ATX socket with the board powered on. ATX pinout can be found at pinouts.ru, for instance. 3. Make sure the beep code refers to PSU and not RAM, CPU, videocard or anything else; 4. Remove extra RAM, HDD, floppy or other non-compulsory peripherals 5. replace/remove videocard 6. Check 'clear CMOS' jumper position 7. Make sure CPU fan is connected to its designed socket and not to case fan socket

Thank you. Just as I suspected it appears to be a third-party utility. I know about Monogram, actually I've tried it yesterday after installing xmllite which was missing. Unfortunately it wouldn't work with that FLAC track (on my system). Apparently we're talking about different (but related) things. Monogram Multimedia s.r.o. seems to be the maker of GraphStudio which I tried with no success. Can't find any dsconfig there though.

madFLAC is a separate package, same as ffdshow, therefore each of them should have their own settings and contol panels. Since I couldn't find a way to trigger one in madFLAC, I assume it's a third-party application that manipulates certain registry keys pertaining to madFLAC. Can you please tell me what the command line is for madFLAC in it's control panel shortcut created by K-Lite? Or is it a generic control panel that controls all codecs installed by the K-Lite package?

I have ffdshow 3562 manually installed (no K-Lite), Start Menu shortcuts modified to use standard 8.3 paths without quotes and the control panels display properly in 98SE. As mentioned in the other topic, paths have to follow the 8.3 format where there are spaces in the file/folder name. Actually all the control panels belong to a single file: ffdshow.ax. This one does not require any KernelEx compatibility, at least on my system. Other libraries in the ffdshow folder do. Looking through its exports I noticed configureAudioRaw which opens a separate control panel that does not appear in Start Menu after standard package installation. For this I just duplicated an already path-modified Audio shortcut and changed the parameter from configureAudio to configureAudioRaw. Full command line is: C:\WINDOWS\SYSTEM\RUNDLL32.EXE C:\PROGRA~1\ffdshow\ffdshow.ax,configureAudioRaw Still, until now I had no luck playing that file. After uninstalling coreFLAC, GOM either throws an error related to ACM Wrapper::Output or simply "can't play this file". ffdshow doesn't even seem to attempt to load, not even in MPC-HC set as Preferred. Is there a control panel for madFLAC? I can't find an entry point to call in madFLAC.ax.

What I don't get is why would you want so hard to use K-Lite in this situation, when standalone versions of ffdshow are available from its official repository or alternative old version repositories. As I said, I don't like the fact that K-Lite is password-protected and cannot be analyzed or partially extracted. Personally I've had a lot of problems with certain codecs during the years and I'd rather not mess them all up with a package I cannot control the way I want. But well, that's only me. As for the K-Lite setting regarding uncompressed format decoding, I guess it's the same thing with the one in ffdshow's control panel > Codecs > Uncompressed.

Just look at the strings in shortcuts. if there's no RUNDLL32 call before the ffdshow.ax, it may not work due to many missing functions (Kext may help with that). Older versions run it through RUNDLL32, newer ones don't. Not sure at which version they made the switch.

Admittedly the Family/Model/Stepping string is not of much help but it's better than nothing anyway. I once was interested in the CPUID function and its proper usage but when I saw all that mess I quickly left it for dead. Maybe at some point I'll take on it again and at least build an external tool to fix that string. But for now that's just wishful thinking.

Go to Control Panel > Network and if Primary Network Logon is not Windows Logon, switch to it in the dropdown box. it will probably ask for some system files unless it can find them by itself (don't allow to overwrite newer files). It will probably also ask for a reboot; do it. If necessary, after reboot go back to TweakUI and make sure the Logon automatically option is enabled as mentioned above.

Hopefully I didn't come across as rude, I was just too tired and frustrated due to all of the problems that seem to pile up day by day. The file we're testing with is actually just the handle for a principle: "I don't need this now, but if I ever do I wanna be sure I already have the means to perform the operation". That's about the whole idea behind these tests. Now, one thing I did was workaround the GetLanguage() error in GOM. It turned out it was an xml file dated back in 2006 which called that function (which apparently is not available on my system) and moreover a variable was misspelled (lnag instead of lang) - yes ever since 2006! I'm talking about GOMPlayer\CodecFindSkin.eng\skin.xml. What I did was replace lang = GetLanguage(); with lang = "ROM"; (one can use any country code, such as "ENG" or "DEU" but careful if you choose KOR, JPN, CHT, CHS, RUS or ESP, because these require the respective set of images to be present in their own directories (the file is pretty easy to read and understand). If you only see an eng folder next to skin.xml, then just set lang = "ENG"; (note the trailing semicolon). Anyway, that fixed the error messagebox and allowed the actual error message dialog to display correctly, not empty (the one that offers to find codec, show details or close). So if anyone comes across such issue, you now know how to fix it. Now, I have not installed K-Lite. I'd rather do things knowingly, step by step, for better understanding of what's going on. The fact that it's password-protected doesn't help either. So I've installed different versions of ffdshow (clsid builds from official SourceForge repository) plus madFLAC 1.10 from the Doom9 forums linked above and played with settings. In audio decoder config > Codecs I set FLAC to either disabled or libavcodec and Uncompressed to either disabled or all supported. In Profiles / Preset settings > Processing I either enabled or disabled 32 bit floating point. In Profiles / Preset settings > Output I disabled 32 bit integer and 32 bit floating point and also switched Connect to to either WaveOut, DirectSound or any filter. None of the combinations made any difference. I even added manual selection of filters, adding madFLAC and/or ffdshow in GOM and MPC-HC settings and still no budge. So you can see where all this frustration comes from. There must be something else wrong with my system. The only way that specific 24bit/192kHz FLAC would play with major stuttering is in VLC with the settins matching those described by Nomen above. Since apparently everyone else here tested this file and players with much better hardware, I came to a partial conclusion that my CPU might just not be up to the task, as it only supports MMX and SSE, nothing more. Whether I'm right or wrong, I don't really know. Now, you asked about the ffdshow control panels. I've has that issue too and downgraded a few installations before realizing where the issue was. Apparently, the shortcuts created in Start > Programs > ffdshow are using full path enclosed in double quotes for the Target field. And everytime the darn thing wouldn't fire up. So I finally replaced the full path with standard 8.3 path, losing the double quotes. So from this: C:\WINDOWS\SYSTEM\RUNDLL32.EXE "C:\Program Files\ffdshow\ffdshow.ax",configureAudio I got to this: C:\WINDOWS\SYSTEM\RUNDLL32.EXE C:\PROGRA~1\ffdshow\ffdshow.ax,configureAudio and the codec control panels showed up right away. There's no need to modify the Start in path. But please be aware that this control panel uses ffdshow.ax, which - depending on version - may require registering and may also require XP compatibility mode (and I'm not sure it will work even then - see missing dependencies). I currently have build 3562 installed and control panels working correctly. This may be true for Haali and other control panels, but it's up to you to test, since I don't have those installed here. Hopefully all this is not just wasted web space. That's about all I can do, at least for now. Good luck, guys!

I give up. No matter what I do, it won't play. I installed madFLAC 1.10 from here, changed and mixed settings in ffdshow, MPC-HC and GOM, to no avail. Uninstalling oggcodecs left some media subtypes uncovered because it didn't delete those registry keys. The author of madFLAC says it's both a source filter and a decoder so it doesn't need ffdshow (read the Doom9 forum topic). I'm at a loss and would rather use my time on something more meaningful. Sorry...

Funny thing rev4464 is not listed in the available versions at SourceForge. I'm gonna try 4466. Currently I was trying the very latest 4525 manually but it may be more than just a ffdshow issue on my system. That darn GOM error is getting on my nerves.

Which version of ffdshow is that? Maybe we can install just that one instead of the whole K-Lite package, if we can find it. Can you believe they actually put a password to the K-Lite codec pack so it can't be extracted manually?!

Mine doesn't crash, just displays an empty About dialog after the undeclared function messagebox. It remains usable. FileHorse doesn't allow me to download through FlashGet. I noticed the same system recently at YouTube. They are slowly but steadily destroying the Internet. Nevermind, I was out of (incorrectly reported) free space on a network drive.

GOM Player needs an external codec to play FLAC even on XP (mentioned that somewhere above). It does have an output choice in Preferences > Audio >Audio tab --> Output device setting, but I'm not sure if it works correctly or if the currently installed FLAC codecs support WaveOut. I've tried oggcodecs 0.68/0.73/0.81 from illiminable (now opencodecs - Xiph) to no avail. Maybe my CPU is not up to the task. With the referenced FLAC track, my GOM is spitting a script error lang=GetLanguage() - undeclared function and the subsequent dialog is completely empty. Can you please tell where you got all those GOM versions from? I don't have 2.1.49 and 2.1.50 (my auto-update is off). Oh and you just gave me an idea for an installer script.

I see. Thanks for the screenshots schwups, it's clear now: VLC automatically switches the output to first/best available. I had set DirectX output in settings but the modules tree stills shows waveout for the respective FLAC upon playback. In Messages I have: main error: ES_OUT_SET_(GROUP_)PCR is called too late (pts_delay increased to 1000 ms) main error: ES_OUT_RESET_PCR called (sorry for the large image size, Internet is not what it used to be anymore) My 98SE machine has a VIA Apollo Pro / VT82C596 chipset and the soundcard is C-Media CMI8738 with Diamond Multimedia drivers v5.12.01.0046.5.1. As mentioned before, CPU is Intel PIII EB Coppermine 667MHz/133 FSB/256kB cache (MMX, SSE).