jds

I don't have any BluRay hardware, but files/content > 4G are nothing new, they also exist on DVD. In the case of DVD, the content is represented in chunks of just under 2G each, and you can copy and play these (*.VOB) files seamlessly with software such as VLC. Can't the same be done with DVD? Even if (and I don't know) BluRay content is monolithic, surely one of those special copying programs should be able to transfer this content in a similar manner as for DVD? I realize this isn't a general solution, but if the main application for such huge files is BluRay content, this would mostly solve this > 4G requirement. Perhaps adding support for > 4G (using similar file spanning techniques) to some key applications would meet the more general requirement, without the tricky task of hacking the O/S to add such support (and in the process, breaking some existing applications as a side-effect). Joe.

Just a little affair to keep "MSFN Members" occupied during dull occasions. Ah, I see. But it doesn't stop there! Wow! Can the board really be so vulnerable that such benign words have to be censored? Someone needs to give this thing a rethink, its like one of those cartoons where some character is plugging holes in a dike with his fingers. Maybe if re-instate the "u" where it should be.... Point #1 http://www.avolites.com/jokes/queen.htm jaclaz Aha! So that's how MS produced their "International" English dictionaries : A. Start with the American dictionary B. Apply Rule #1 (or #2, which is partly derived from #1) Thus all "ize" endings become "ise", even if they're not supposed to, according to true (aka. The Queen's) English. Most annoying! BTW, I found the thread I was looking for : (this includes info. for FF as well as IE). Joe.

Fantastic! Thanks, that's a great work-around. This must be how wsxedcrfv did it. OK, now I'm confused. Green glass door? Hey, it's as good a theory as any. Makes you (me) worry though, why the board may be vulnerable to such things. Google (et. al) isn't. Joe.

Works for me: "Your search for the term search...javascript returned 537 results" Thanks. This is weird! I've tried again and again get the same error when I use the "Search This Forum" search box. BTW, if I use the "Google Custom Search" search box, I don't get this problem, however the results are then from all of MSFN, rather than this specific forum. Joe.

I remember a topic here about controlling the javascript excesses (eg. CPU time) experienced with many web pages. So, I tried searching this forum for the word "javascript". The result : "The following search terms are not allowed and were removed from your query: javascript" What The ... ?! Joe.

Thank you Mr Loew. As this operates in kernel mode, will it take precedence over FineSSE (or the VC 4.2 debugger), or do I need to uninstall the later from 'win.ini'? Joe.

I installed FineSSE as above a couple of days ago, along with the Flash AX and Plugin 9r289. However, I found that I had to use the "Debugger2" trick mentioned earlier because I had/have VC 4.2 installed. Anyway, soon afterwards I had some issues with Flash, and a message came from FineSSE saying something like, "Too many exceptions, quitting". Next time, I'll try removing the -v option, just in case it's a limitation of the event logging (unless you tell me that won't help). I'll also try to take better note of what pops up on the screen. No. (Unless the app or plugin does some now-useless II exception handling that you would like to avoid, like Flash 9 r289.) Can you please clarify what you mean about Flash 9r289? Is this comment only relevant for pre-P2 machines? I installed P6CPU.VXD on my P1 MMX machine (currently in storage due to renovations) a while ago but it didn't handle all the necessary instructions for mjpegtools, so I'll try FineSSE on this at the next opportunity. Meanwhile, is P3CPU.VXD available to download, to test for the P3 issues (such as SSE) for later builds of Flash 9 (and 10, from the testing I did preciously)? Joe.

Fantastic! A solution to both the 686 and SSE instruction problems! I never did solve the PNG2YUV tool by rebuilding, so this will come in handy for that situation (the PC concerned is currently in storage due to renovations, so it'll be a while before I can try this). Of more immediate interest is the SSE capability, to help with the recent versions of Flash Player 9. The PC concerned is still in regular use, so next time I get a crash with Flash (hmmm, the rhyme seems appropriate), I'll install FineSSE and check if the problem goes away. Joe.

Hmmm ... that hologram and "X05" seem similar to the mystery CD-ROM that was once discussed here : Joe.

Clues : 1. http://forum.aveotek.com.tw:8080/phpbb3/viewtopic.php?f=8&t=3&sid=33c99c2e681eefc3f6d2dc77ab812c07 2. http://york.wikidot.com/usb-video So maybe this USBCAMD driver from the 98 DDK (as mentioned in #2) can be adapted by editing some INF file with the appropriate VID & PID numbers? Or maybe another OEM's 98 driver could be similarly adapted? Joe.

Thank you very much for that explanation, I've copied and saved it as "UBCD.txt", so when the need arises (hey, I ain't game to try this stuff on a working system;-) I'll be sufficiently enlightened to know what I should do (and have some control over the outcome). Joe.

Your wish is my command... ;-)I've added a new FYI into the 1st post concerning innounp + Inno Setup. Also added strike-out lines over old, invalid links. HTH Thanks, M.D. Glad to see someone is maintaining this thread! Joe.

FYI, Last night, I discovered a new place where disk space can leak. I have a directory called "%windir%\internet logs" and it was wasting almost 450M. It's used by Zone Alarm (if you have it), but all the similar reports of such problems involved a couple of the files there growing out of control. However, this was not my case, instead there were a whole bunch of *.TMP and *.ZIP files, of up to about 50M each. Viewing the log data in Zone Alarm only showed about 20 entries, going back as far as 2 Jan 2011. So I added a margin of 2 days to this and deleted everything that was older than 31 Dec 2010. Zone Alarm didn't complain, so it didn't have these files open, and the same log entries were shown in ZA afterward, so that was OK too. I think that at times, when Javascript and/or Flash garbage has locked my browser, and I have to use the Vulcan Nerve Pinch to terminate the session, stuff that was passing through Zone Alarm's hands must have simply been abandoned and accumulated in this directory. Perhaps it's used if/when I restart the browser and choose the "restore session" option. Maybe. In any case, this is where those mysterious Megs had disappeared! Joe.

At first I thought, why copy the win98 directory to the HDD to run it from there, why not simply run 'setup.exe' from the win98 directory on the CDROM? But I figure there'll be some reboots that would cause the 'setup.exe' in the root directory of the CDROM to be invoked, right? Also, if you format the HDD, don't forget the "/s" option to put the system files there. Finally, I presume using the UBCD in this way would be analogous to simply using a standard W98SE CDROM, albeit a bit less convenient. Joe.

Can you give some clues here? I attempted to guess at this with the help of the Internet Archive, but my attempts were redirected into a download of Avast 5, which was not what was wanted. Now I'm wondering if the download link for the 4.8 Pro version might do likewise ... Joe.

Nothing is missing. Some stuff is PnP and invokes the New Hardware Detected wizard, other stuff isn't and it's either on the "well-known-devices" list that MS-W scans for during installation or else you have to manually install via the Add New Hardware wizard later. The former will have a PnP ID, the later won't. Joe.

Hi Joe. I did find this: http://www.driverssoftware.com/drivers.php/data-modem-cdma-6803-driver/70037 and http://www.baltia.net/en/nodes/view/594 Those are C-motech Rev. A modems (USB) that support Win98. So, I'm downloading those drivers and just need to make a few edits? This would be awesome if it works. Maybe. You need to check the VID&PID codes in the INF files, and using USBView, the VID&PID codes as seen via USB. Then we may see if they match or have a chance of being compatible (identify the relevant chipsets and see what information is out there about them). Why? Because it has the word "Universal" in its name? Joe.

Apart from the complexity of the task, the main problem is that the necessary technical information is not publicly available. However, since this is CDMA and not WCDMA (UMTS), I believe W98 drivers were available at one time. These things are all based on Qualcomm chipsets, and I think I've seen W98 drivers for a C-motech (Korea) model. Once you've found such a driver, you may need to edit the INF files if your model's VID (might be the OEM's instead of Qualcomm's) and PID value differs, just try to confirm it's the same or compatible chipset. You can use Intel's USBView utility to see what you've got. Joe.

Unfortunate about the UBCD, but MSFN has to protect its interests, so I understand. I downloaded it a couple of months ago, just in case, but haven't had a need to try it (or the time to delve into it). I wasn't aware its scope was so broad, actually. Anyway, let's ignore any bundled applications for the moment. I rediscovered the A-P thread recently, and did read a moderate portion of that tome, I think I recall some discussions about improving compatibility with the Unofficial Service packs, and had thought this had been achieved. Am I wrong in thinking that about the A-P compatibility, or is it that the same level of compatibility was not achieved with the updates in the UBCD? Do you know to what extent the UBCD can be applied without introducing compatibility problems with either 98SE-SP-xxx or WUPG98? And KernelEx? No! Problem has not solved but no one interested to solve this problem so i am loosing any hope. by the way thanks to all. We're trying to figure it out. Joe.

That's funny, the first thing that came to my mind, is that you should scan for nasties. If that's not the problem, check (no, I'm not sure how) that %windir%\system\conagent.pif and %windir%\pif\command.pif (and there may also be a '_default.pif' and several 'MS-DOS Prompt.pif' files somewhere) aren't corrupted. Joe.

Just found a new candidate : http://www.bitdefender.com.au/PRODUCT-14-au--BitDefender-10-Free-Edition.html A long-standing and respectable anti-virus house, and this package lists W98. Edit : Bummer, this free BitDefender version is an on-demand scanner, no real-time protection. However, Avast 4.8 Professional is still available (for the moment). Joe. PS. Some updated info on Avast 4.8 ... :

I guess you'd want to boot some sort of "Live CD" and maybe run or install (probably to RAM disk) some sort of virus checker, so the nasty isn't active for the install or scan. However, the RAM disk created by the "Live CD" might be too small, depending on the particular anti-virus package. Of course, your choice in "Live CD" O/S will dictate which anti-virus packages are available for this. One thing you may as well try, if the above isn't feasible, is the DR-Web DOS anti-virus package. Boot from floppy or CD with DOS, create a new directory on the hard-drive, extract the anti-virus there and run it. Make sure not to invoke ANY other stuff on the hard-drive, just to be safe. If all else fails, you may as well try to install and run an anti-virus package with the system infected. Until now, Avast 4.8.1368.0 would be the choice package, but it's not available for download anymore, and who knows what you might be downloading from an untrusted site [ edit : actually, avast 4.8 professional edition is still available, you can trial it for 60 days, see http://www.avast.com/en-eu/download-software#tab3 ]. So my suggestion would be : http://www.bitdefender.com.au/PRODUCT-14-au--BitDefender-10-Free-Edition.html (a respectable anti-virus vendor, and this says it supports W98) Joe.

Oh, I didn't know that. Placing new versions of files that it already knows about (ie. superseding those in the CAB's) I do recall reading about. I guess it's similar to the concept used with the VMM32 directory vs. the VMM32.VXD monolith. So if you can simply place new drivers in the \WIN98 directory, then problem solved! :-) Joe.

If you ask because of the duplicate threads, dencorso has already fixed this by merging them. If it's because you have solved your problem, could you please give a little feedback? @ submix8c : I thought UBCD basically added extra drivers for newer (newish) hardware. Why would this cause problems for using KernelEx and/or RP (especially interested in the former, as I don't use the latter)? Joe.

Well, I don't know much about slipstreaming, but ... MS often added new drivers to their install CD in a separate directory structure called "\drivers", to which you could then direct the wizard when prompted. I wonder if that's sufficient? Also, the command "start whatever.inf" should install a driver (ala. method 1) when the O/S is running, not sure about during the O/S installation process though, nor where you'd put such a command. Joe.