RetroOS

Okay, I thought everything was running fine with Dec 2007 Final... However, since I updated (only JSCRIPT.DLL was newer for me), I got an empty square window appear often while using Internet Explorer. I had to close it (using the 'X') to continue. I figured it was probably when JSCRIPT.DLL was being called? It sounds a bit like what some others have posted recently. However, I did not get any installing or crashing, just an empty window. So... I deinstalled Java 6 Update 4 and reinstalled Update 3 that I had earlier. I also back-dated JSCRIPT.DLL to the previous version I had, then de-registered and re-registered it, and rebooted. No change! This is really weird since at this point everything should be as it was when it worked!!! Rolling forward again, I removed Java 6 Update 3 and reinstalled Update 4, and reinstalled the Unofficial Scripting 5.6 update again. No change as expected. So! I downloaded the Unofficial Scripting 5.7 update from MDGx and installed it. ...No problems so far! The only thing that bugs me is that I recall some discussion a while ago regarding Scripting 5.7 having problems in Windows 98SE... I'll have to locate the discussion and see what the issues were. The conclusion is that I do not know what made my 98SE go silly on me... But Scripting 5.7 fixed it... On a side note, I also found that Windows was creating a bootlog.txt files every time I used Windows and updating it during use and closing Windows. All this was adding some overhead to Windows. I had one font error (explained in another topic) that I resolved, but this did not stop the bootlog.txt being created. In the end I had to put the Disablelog=1 option in the MSDOS.SYS file... I had noticed the logging over some time, but thought maybe it was from a crash or something... I don't know when it started doing this... Maybe RP7 or 98SE2ME? Anyone else noticed continuous boot logging?

Hi Fredledingue, What is the chipset of your Mobo? If you're not sure, check in Device Manager, System devices, and check for the likes of Intel, VIA, SiS, and so on. If you know the actual chipset model or name would be even better. You may need to install or reinstall chipset drivers. Also check in Device Manager for any yellow exclamations (!) on any devices.

I've had an error logged in the Windows bootlog.txt file for some months. It stated that the file CAMBRIA.TTC failed to load. At first I thought this was an incorrectly named TTF file... So, I renamed the file and registry entries to CAMBRIA.TTF... No change. So then I copied the font file and deinstalled the font... Problem gone. I attempted to reinstall CAMBRIA.TTC into Windows Fonts but it would not install... After a little digging, I determined that TTC files are TrueType Collection files that contain multiple TTF fonts. Then after some more digging, I discovered that CAMBRIA.TTC is installed with Office 2007... So... Even though I deinstalled the Office 2007 Compatibility Pack, it left fonts behind. I also found out that Microsoft created a utility called BREAKTTC that separates the TTC file into individual TTF font files. BREAKTTC was part of the Microsoft TrueType SDK... Problem is that the Microsoft TrueType SDK has been removed from the developer area of the Microsoft FTP Site... Anyway, I located a copy of the SDK (ttsdk.zip) and used BREAKTTC.EXE to create the two TTF files that I called CAMBRIA.TTF and CAMBRIAM.TTF(Cambria and Cambria Maths). These two TTF files install and work with no problem in Windows 98SE. The odd thing is that the BREAKTTC utility is from 1994 and the SDK itself is from 1996. The only Windows around in 1994 was Windows for Workgroups 3.11 and Windows NT 3.5... It's a mystery why the TTC file would not work in Windows 98SE... So, if anyone has been playing around with the Office 2007 Compatibility Pack and has noticed a font loading error with CAMBRIA.TTC, then here is the fix!

Hi Offler, See this similar topic I started: http://www.msfn.org/board/Visual-Studio-20...9x-t112283.html Maybe there might be some way of getting the libraries of C++ 9.0 to work in 9x?

Hi Eck, I deselected Shockwave and Flash at Windows Install time, and then installed current Flash after - so I've never had Shockwave installed or the old Flash files. Now, to fix these Flash crashes, do these steps: 1. Download the Flash Player Uninstaller from here: http://download.macromedia.com/pub/flashpl...lash_player.exe 2. Download the Shockwave Player Uninstaller from here: http://fpdownload.macromedia.com/get/shock...uninstaller.exe 3. Run the Flash Player Uninstaller followed by the Shockwave Player Uninstaller 4. Reboot 5. Delete the MACROMED folder in C:\WINDOWS\SYSTEM (or whatever your Windows system folder is) 6. Install current Shockwave Player ActiveX (and Netscape plugin if using Firefox) 7. Install current Flash Player ActiveX (and Netscape plugin if using Firefox) 8. Reboot 9. Flash Player 9.x install now cleans up the previous version flash files left behind.

I should clarify that I only have Flash Player installed and not Shockwave Player... Another possible variable?

Hi Eck, Check your version of BROWSEUI.DLL. Mine (the good one) is 6.0.2800.1914. If you have 6.0.2800.1915, then it did not get back-dated when you removed the IE cumulative update. Microsoft has just released IE6 SP1 Cumulative Update kb944533. See http://support.microsoft.com/kb/944533/en-us It releases with BROWSEUI.DLL version 6.0.2800.1916. It has fixes for JSCRIPT.DLL related problems as well. So, when the person who is compiling the unofficial IE CU releases it, I'll see whether the newer files all work okay... Rock on updaters!

Actually my kb942615 variable might have some merit... Just need to release a version with the older BROWSEUI.DLL from kb939653...

Okay, first off: I'm a naughty boy! Wack! Wack! Wack! Second is that I have installed Dec 2007 Final. The Twain98 loop is gone. Probably because the timestamp has been changed on the four files which caused them to install... The SYSTEM.ini tweaks menu does not give me any more errors. Since I had the problem with the current settings being wrongly detected, I can no longer fault this... However, it is still using a way to high MaxFileCache for over 1GB RAM... I'm still running kb942615 with BROWSEUI.DLL from kb939653 with no problems. This could be the variable for the problem below that I do not experience even with Final installed. Okay folks, the post RC1 AP contains one updated file in the SCR569X update. JSCRIPT.DLL has changed from 5.6.0.8832 to 5.6.0.8834. BTW, JSCRIPT.DLL plus the four changed Twain files are the only ones that installed for me since RC1. Well, everything works for me but see note above regarding IE update. Once last thing. Something I should have mentioned ages ago. I am using MFC42.DLL 6.2.4131.0 (in C:\WINDOWS\SYSTEM). The version that comes with V_Studio unofficial update is 6.0.9782.0... I've had the newer version installed for a long time and never had any problems. I don't even know where it came from. I suspect it was from a Microsoft Platform SDK install. Has anyone ever heard of MFC42.DLL version 6.2.4131.0?

Well... It's definitely running the Silicon Image drivers... You could try using soporific's Auto-Patcher 98 to update all the system files: http://www.msfn.org/board/index.php?showtopic=80800 It's a fairly big download though... Got DSL/Cable?

I've been running Java 6 Update 3 and now Update 4 (BTW fixed a web page I had a problem with...). I have never had the mentioned problem. However, I'm not sure if I have the unofficial scripting update installed. When did you include it in AP? - I've installed up to Dec 2007 RC1 but have not installed Final (or RC2) yet.

Maybe then, this topic should be called Visual Studio 2008 and Visual Studio 2005 and Windows 9x... In that case, KernelEx may already solve some VS2005 problems... If I had time, I would do some work with the KernelEx source... Time, time, time, never enough!

Old? Over 30? Go into Device Manager under System in Control Panel. Change the view to Device by connection. Expand the tree and check where each drive connects to. You may have to expand a number of lines to find the drives. You will find a controller listed, then a channel, then the drive. On the controller that each drive connects to, select Properties and check the driver. Post controller name, driver name and date, and connected drive names if you can.

Well, you might as well install the rest of Auto-Patcher 98 updates. I've got all of Auto-Patcher (excluding manual installs folder) installed and currently my 98SE is stable with no audio or video issues. You may find that it all works okay after that.

I had heard that. The problem with VS2008 is that you cannot just change compile options to get it working... It simply will not work in Windows 9x. It would be good to get some heads together over this one with the purpose of finding some kind of workaround for VS2008 compiled software. As mentioned previously, maybe some concept like the way KernelEx operates by expanding the Windows 9x API set. Even if those API functions are 'simulated' with close 9x functions or simply returning a successful status if applicable.

Hi FirstOff, Welcome to MSFN! Can I assume that you had this problem before you used Auto-Patcher 98? You could try the unofficial nVidia 82.69 drivers. See here: http://www.msfn.org/board/index.php?showtopic=97140 Download here: http://www.mdgx.com/files/NV8269.EXE I use them with a FX 5200 with no problems and a bit more performance from the 81.98 official drivers. I have an original Live! card with current drivers on a VIA chipset Mobo. Make sure that hardware acceleration is set to full for both audio and video. Also, sometimes Creative sound cards do not like being in PCI slot 1 on the Mobo. You will probably have to check your Mobo manual to find slot 1. Go to http://www.sis.com/download/ Download and install the current SiS AGP GART driver 1.21 (assuming you are using AGP) and the current IDE driver 2.04a. After installing, check in Device Manager, that the hard drives and CD/DVD drives actually are using DMA. Non-DMA access uses the CPU for every byte transferred to the device and causes a lot of overhead.

Microsoft Visual Studio 2008 was released late last year. According to http://msdn2.microsoft.com/en-us/library/bb531344.aspx, Windows 9x is no longer a supported target platform: The Windows 95, Windows 98, Windows ME, and Windows NT platforms are no longer supported. These operating systems have been removed from the list of targeted platforms. The typical message upon running a VS2008 compiled application that uses 0x0500 in the WINVER macro is: (For more information on WINVER macro see: http://msdn2.microsoft.com/en-us/library/aa383745.aspx) Error Starting Program The [full path of executable] file expects a newer version of Windows. Upgrade your Windows version. Following this is: [full path of executable] A device attached to the system is not functioning. This second information box would appear without the first if WINVER macro was still 0x0400 in a re-compiled source. Either way, it no gonna run... One person has determined that the Win32 API call GetSystemWindowsDirectoryW in KERNEL32.DLL was being referred to even with a simple application. See http://forums.microsoft.com/MSDN/ShowPost....93&SiteID=1 Maybe this is where a KernelEx solution could be useful. This spells the end of new software for Windows 9x since most software developer for the Windows platform code in Microsoft C++ under Microsoft Visual Studio. Windows APIs are taylored for C++ calling conventions and data types. I personally code entirely using Microsoft Macro Assembler (MASM) which supports high level syntax and C++ conventions. Contrary to popular belief, MASM is not just for writing modules to plug into C++. It can be used to write an entire PE EXE, DLL, and so on. See here for more information: http://www.masm32.com MASM version 8.00 that comes with Visual Studio 2005 still supports Windows 9x. Has anyone looked into this problem?

Actually, if you read the first post carefully and follow the instructions, you will be able to get the same reaction in 2000 and XP!

Some more: Network Adapter Drivers LAST - FREE - Broadcom NetXtreme Network Drivers 10.24d --- http://www.broadcom.com/support/ethernet_n...eme_desktop.php LAST - FREE - Broadcom NetLink 57xx Network Drivers 10.24d --- http://www.broadcom.com/support/ethernet_nic/netlink.php LAST - FREE - Broadcom NetLink 4401 Network Drivers 4.60 --- http://www.broadcom.com/support/ethernet_nic/4401.php Emulators and Utilities ONGD - FREE - MameUI32 - Multiple Arcade Machine Emulator --- http://mame32qa.classicgaming.gamespy.com/ LAST - FREE - ClrMamePro 3.109a - Mame Data Manager --- http://www.mamechannel.it/files_support/cmp3109a.zip Connectivity LAST - FREE - Nokia PC Suite 5.8 --- http://nds2.nokia.com/files/support/nam/ph...Suite_58_en.exe Windows Components LAST - FREE - Microsoft Font properties extension 2.1 --- http://download.microsoft.com/download/e/f...fcbf/ttfext.exe

I see it all the time on 'newer' Windows versions... But since I see it all the time, I just cannot recall if I see it on my 98SE box... I'll keep watch on 98SE...

Look on the second post of this topic and you will find a link to Avast! 4 Home virus scanner. It's probably one of the fastest and it works in 98. You will need to register for a product key, but registration is free and lasts for 14 months. After that you simply re-register.

Yep! Since it uses 32-bit code along side 16-bit code in the kernel (and other files), it not gonna go on a 286... In fact, DirectX 8.0a won't install without a Pentium-class CPU... Unless you short circuit the installer CPU detection code... Then it worked without a problem on a 486 - Gotta love Microsoft! I did not have a 386 at the time to test it. For more information see: http://support.microsoft.com/kb/819696 Specifically this statement: "DirectX 8 and DirectX 9 do not support systems with 486-class processors." in the Prerequisites section. While on the subject of DirectX, I recall that MS released DirectX 6.1 with a suite of updated video drivers similar to Windows 98 and then dropped them in 7... So to get the new fast DirectX video drivers, 6.1 had to be installed and then 8.0a... Go hardcore 95'ers! - I hung up my 95 hat when 98SE was released but don't feel bad - You're all part of the 9x family!

Actually there is PCIe only if the chipset manufacturer still provide newer chipset drivers like VIA. And, yes, there are some new video adapters that won't work like newer ATI ones. Here are some good topics to read about getting newer hardware and software working in Windows 98SE: http://www.msfn.org/board/index.php?showtopic=107001 http://www.msfn.org/board/index.php?showtopic=78592 http://www.msfn.org/board/index.php?showtopic=109574 http://www.msfn.org/board/index.php?showtopic=71476 http://www.msfn.org/board/index.php?showtopic=105936 http://www.msfn.org/board/index.php?showtopic=97588 http://www.msfn.org/board/index.php?showtopic=97140 http://www.msfn.org/board/index.php?showtopic=105373 http://www.msfn.org/board/index.php?showtopic=105725

Java 6 Update 4 is working without a hitch in 98SE. Here is the warning text from the install (note the 'for best results we recommend' bit): Warning: This is not a supported Operating System Thank you for choosing the Java(TM ) Platform. You may continue with this installation, but for best results we recommend running on one of the following operating systems: Windows XP Professional (SP2), Windows XP Home (SP2), Windows Server 2003, Windows 2000 Professional (SP4+), and Windows Vista.

...The only problem here is if the user has one of those 'higher' versions of OLEAUT32.DLL AND they have the latest OLEPRO32.DLL -- AP will think its installed. Is this likely to happen? Hi soporific, One problem that is ready to jump out and bite me, is that because of the OLEAUT32.DLL versioning quirk, the lastest compatible version of the file actually has a slightly lower version number but is newer! If anyone has an even higher version than 2.40.4522 of OLEAUT32.DLL installed then it won't be for long! Sure there is MD5 checking as mentioned, but this only checks if a file is already there but is no use for versioning... The other aspect of checking is the file date. OLEAUT32.DLL 2.40.4519 is newer (31 July 2006) than 2.40.4522 (19 June 2003). Most system files will maintain the original file timestamp. Some files however, will change to the install date (and increase size...), for example some of the Internet Explorer 6 SP1 files. It's some type of serialisation process of the files during install. Not sure why...