RetroOS
Content Type
Profiles
Forums
Events
Posts posted by RetroOS
-
-
...So what MS is saying in MS article 181594 is just in theory. A blind assumption...
Yep! In 1995 when Windows 95 was released, no one would have thought of ever having 2GB of RAM!
I find it quite ironic that Microsoft have not updated or removed those 'accurate' docs!
Windows 98SE with 1.5GB of RAM has been working well with the settings I mentioned.
I've been looking through the VMM.VXD module lately... It's one hundred thousand lines of code!!!
I'm trying to work through the DOS entry point so I can determine how it's setting up the memory management when it goes into protected mode...
Oh well... I'll keep chipping away at it as I get time... (that elusive thing
)That's just the beginning though...
Then, with more than 1GB of RAM, there is all the modules memory management and allocation bugs that were never fixed by Microsoft... (what bugs? 9-what? What are you talking about you silly little man!)
0 -
Hi Offler,
I'm not sure what makes the option appear...
I have however found the registry entry.
In regedit, go to the following registry key:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced
If the entry TaskbarSizeMove does not exist then create a new DWORD Value.
Make the value 0 (zero) for locked and ff (in hex) for unlocked.
The only catch is that Explorer has to refresh to pick up the change...
You may need to restart Windows to take effect.
If that does not work, then there must be some updated files involved...
If it does work, then you can automate it with the two following .reg files.
Just copy the text and paste into a text file.
Save the two files as something like Lock the Taskbar on.reg and Lock the Taskbar off.reg.
Double-click on one of the files and respond Yes to import then restart Windows
Lock the Taskbar on.reg
REGEDIT4
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced]
"TaskbarSizeMove"=dword:00000000Lock the Taskbar off.reg
REGEDIT4
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced]
"TaskbarSizeMove"=dword:000000ff0 -
More!
Thought I would put in some more commercial software as well.
Firewalls
LAST - $$$$ - Norton Personal Firewall 2005 --- http://www.symantec.com
LAST - $$$$ - Symantec Desktop Firewall 2.0 --- http://www.symantec.com
Virus and Spyware Scanners + Privacy and Security Tools
LAST - $$$$ - Norton AntiSpam 2005 --- http://www.symantec.com
LAST - $$$$ - Norton Internet Security 2005 --- http://www.symantec.com
LAST - $$$$ - Norton Password Manager 2004 --- ftp://ftp.symantec.com/public/english_us_...updates/NPM.exe
Windows Utilities
LAST - $$$$ - Norton CleanSweep 2002 --- http://www.symantec.com
LAST - $$$$ - Norton GoBack 4.0 --- http://www.symantec.com
LAST - $$$$ - Norton Utilities 2002 6.0 --- http://www.symantec.com
Hard Disk Utilities
LAST - $$$$ - Symantec Ghost 9.0 --- http://www.symantec.com
LAST - $$$$ - Norton PartitionMagic 8.0 --- http://www.symantec.com
Connectivity
LAST - FREE - Citrix Presentation Server Client Package 9.246 - 9.237 available from --- http://www.firstdatasystems.com/support_downloads.php
LAST - FREE - Microsoft Remote Desktop Connection Software XPSP2 5.1.2600.2180 --- http://www.microsoft.com/downloads/details...;DisplayLang=en
LAST - FREE - Microsoft Remote Desktop Web Connection XPSP2 5.1.2600.2180 --- http://www.microsoft.com/downloads/details...;DisplayLang=en
LAST - $$$$ - Norton Web Services --- http://www.symantec.com
LAST - $$$$ - pcAnywhere 12.0 --- http://www.symantec.com
LAST - $$$$ - Procomm Plus 4.8 --- http://www.symantec.com
LAST - $$$$ - TalkWorks PRO 3.0 --- http://www.symantec.com
LAST - $$$$ - WinFax PRO 10.02 --- http://www.symantec.com
LAST - $$$$ - WinFax Basic 10.02 --- http://www.symantec.com
Storage Drivers
LAST - FREE - Silicon Image SiI3x12 PCI to 2 Port SATA150 IDE Driver 1.2.0.57 --- http://www.siliconimage.com/docs/3112A_x86..._idvr-12057.zip
LAST - FREE - Silicon Image SiI3x12 PCI to 2 Port SATA150 SATARAID Driver 1.00.51 --- http://www.siliconimage.com/docs/SiI3x12A-...ID%20Driver.zip
LAST - FREE - Silicon Image SiI3114 PCI to 4 Port SATA150 IDE Driver 1.2.0.5 --- http://www.siliconimage.com/docs/3114_x86_...e_logo_1205.zip
LAST - FREE - Silicon Image SiI3114 PCI to 4 Port SATA150 SATARAID Driver 1.0.0.8 --- http://www.siliconimage.com/docs/3114_x86_..._raid_1008b.zip
LAST - FREE - Silicon Image SiI0680x PCI to 2 Port IDE/PATA IDE Driver 1.0.0.12 --- http://www.siliconimage.com/docs/SiI0680A_Windows_IDE.zip
LAST - FREE - Silicon Image SiI0680x PCI to 2 Port IDE/PATA RAID Driver 1.0.1.7 --- http://www.siliconimage.com/docs/SiI0680a_rdrv1017.zip
0 -
Hey Offler,
I can reproduce this 'so Microsoft' CPU hog bug in my 98SE using the built in System Monitor.
What you need is the 'Lock the Taskbar' option from right-click menu on the Taskbar.
The catch is that this option does not exist in native Windows 9x...
I have Tihiy's Revolutions Pack and MDGx's 98SE2ME installed.
I'm assuming that after installing one of these I have acquired the 'Lock the Taskbar' option... Not sure which one or when...
(Maybe it was after Gape's Unofficial Service Pack 2.1a? Or perhaps soporific's Auto-Patcher 98?)
Selecting this option locks the position of any toolbars on the taskbar and removes the sliders.
Deselecting will return them.
Tihiy, MDGx,
Any comments as to why one of those enhancement packs provides the 'Lock the Taskbar' option?
Not even Windows Me has this option!
I'll have to do some experimenting on a new install...
0 -
Hi fishindude,
The following product links indicate support for Windows 98SE and 48-bit LBA using the Silicon Image Sil3112A Serial ATA Controller:
http://www.strattoncomputer.com/scs-s1022-i.html
http://fwdepot.com/thestore/product_info.p...roducts_id/1635
http://www.upgradeware.com/english/product/s1022i/s1022i.htm
Here's a review of the Sil3112A that likewise indicates that it supports Windows 98SE and 48-bit LBA:
http://www.techwarelabs.com/reviews/storag...112/index.shtml
So... Looks like it does indeed support both Windows 98SE and 48-bit LBA!
0 -
Has anyone tried to edit their MySpace account profile under Win98SE, having Java 6 installed and set as default?...
Did you try Update 4?
0 -
...
About MSXML, looking in the System folder I only found MSXML 3 SP7 files but there's no uninstall entry for such package in Add/Remove. I'm not playing any games on this machine so I'm reluctant to installing the recommended MSXML4 just for kicks.
...
Drugwash,
The uninstall instructions only apply to MSXML4 not 3, 2, or 1.
You should install the latest supported MSXML4 anyway.
If you install a piece of software that uses MSXML4, and you don't already have MSXML4 installed, it may install an older and more security vulnerable version...
0 -
...
* MSXML 4.0 -- this should be fixed, uninstall any version later than kb927978, and then install kb927978. RetroOS is the man to turn to for identifying which MSXML we should be using.
Just to clarify, after uninstalling all MSXML4 entries, for example, MSXML 4.0 SP2 (KB936181), from Add/Remove Programs, the actual MSXML4.DLL file needs to be deleted from the Windows SYSTEM folder (normally C:\WINDOWS\SYSTEM) before installing kb927978. Otherwise the file stays the same!
See http://support.microsoft.com/kb/936181/en-us for details.
* InfraRecorder update section gave an 'access denied' error when trying to remove the old version.- anyone else get this?
- RetroOS, was the old version installed by AP? If not, that makes sense.
Yes it was the previous AP installed version.
* The Twain update looped- this should have been fixed in RC2. Can anyone see if they can get it to loop again? Cheers!
Yep, that figures... I never installed RC2.
* There is something wrong with the Visual Basic menu... There is no official VB6 entry and yet I get this in the log- I moved the official VB6 to the Stability Hotfixes module for 2 reasons:
-- 1, It's not optional anymore as virtually everyone will get the superseded message. The only reason it will get installed is if you are using AP on a newly installed OS, or you actually don't have VB6 on your system. Who doesn't need VB6? Is there any good reason not to install it?
-- 2, by moving it out of the VB module we save having to reboot twice when using this module.
Makes sense.
* BROWSEUI.DLL 6.0.2800.1915 from kb942615 kills my Windows Explorer (failure in EXPLORER.EXE), the catch is that I have EXPLORER.EXE 5.50.4134.100 from Revolutions Pack 7.11.- i will revert back to kb939653, problem solved. I'll put a note on my updates list about this. Thanks for being such a useful beta tester.
The only problem was the BROWSEUI.DLL file. I'm still successfully using all the other security patched files from kb942615.
I suggest just replacing the one BROWSEUI.DLL file in kb942615 with the file from kb939653.
That way we get nearly all the security updates.
* have you looked at ASPI Layer 4.71.2?- yes i have and it sucks big time. 4.6 has never failed me yet, 4.71.2 has failed me twice. And others have reported similar, so its a def no. Still, thanks for the suggestion!
Roger!
* Incompatibilities with RP and 98SE2ME- i really don't know what to do about this. I must admit to not testing very extensively with RP (but i do to some degree) but not at all with 98SE2ME. I suppose i should get around to it, but i can see that its going to be lots of work getting stuff to not blue screen on me. Maybe i'll make the next major release more 98SE2ME compatible, but until then i suppose that you 98SE2ME users gotta be careful using AP.
If you were referring to the dialog a couple of posts back, this was really a historical explaination rather than a current problem.
Aside from the BROWSEUI.DLL problem, I have no other current problems with AP and RP/98SE2ME.
0 -
Oooh goody, a new Java 6 update!
I'd been checking regularly but still the Updates Guy bet me to it!
Well, 2008 has been busy with updates for 9x so far!
Windows 7? Bring it on! I know where I'm staying!
MDGx, still holding up Windows 9x in 2008! Man you're good!
0 -
I think that's caused by the installation of EXPLORE98, the MDGx package of the latest combined explorer.exe security patches and improvements, along with the nice Windows Me style icon.
...
When I ran the new version of Auto-Patcher, it detected that the same version of EXPLORE98 was installed and so skipped its installation, which I was happy to see. It had been installed by my run of the October Auto-Patcher.
...
Hi Eck,
With RP installed, AP always skips installing EXPLORE98 update because the existing file is newer.
So, It has never back-dated EXPLORER.EXE.
My guess is that if someone installed the latest Unofficial Cumulative Update for IE6SP1 (kb942615) with the newer BROWSEUI.DLL onto Windows Me, it would do the same thing to Windows Explorer since it is the same file used in RP and 98SE2ME Option 3.
Of course, this version is also dependent on SHELL32.DLL, USER32.DLL, USER.EXE, (and some others as well) from Windows Me.
If any of these files are not from the same version set (98SE, Me etc)... Then BOOM BABY, Windows dies!
I had that problem when the Unofficial Q891711 update was back-dating USER32.DLL and USER.EXE before the installer was fixed.
I've been through all the possibilities, and it just plain appears that the latest BROWSEUI.DLL file is not compatible with Windows Me EXPLORER.EXE and therefore with Revolutions Pack, 98SE2ME Option 3, and anything else that uses Windows Me Explorer.
When I back-date the file to the previous release, everything works again.
0 -
Heh heh. We've been through the ASPI conversation. Almost no one wants the newer versions. When they work it's a miracle. The one in Auto-Patcher improves upon what comes by default with Windows and works all the time. The newer ones do nothing helpful and often just break things.
...
Hey Eck, now you mention it, I recall some years ago when I installed ASPI 4.7x, that it broke my tape backup...
The current improved 4.6 works just dandy!
Sop, have you had a chance to look at the Dec 2007 AP problems I've had?
My post: http://www.msfn.org/board/Auto-Patcher-Win...051#entry732051
The most critical being the BROWSEUI.DLL and Windows Me EXPLORER.EXE breaking!
AP Dec 2007 currently will break Windows Explorer for anyone that has RP and/or 98SE2ME option 3 installed (or any other reason for using EXPLORER.EXE 5.5)!!!
Has anyone else had the Explorer problem with RP or 98SE2ME option 3 installed?
0 -
Thanks for dependency walker. it helped me to analyze so much Dll related problems as possible.
Since this system is being upgraded for long time i was quite dissappointed when i ran the analysis for some crucial applications. It seems that most apps (including explorer.exe) are using shlwapi.dll. This dll is connected to missing, dlls and missing exports which are mostly NT based (as this dll too). Has someone of you noticed it?
Hi Offler,
I ran Dependency Walker on my Explorer.exe and got the same missing exports in delay-load dependent modules of shlwapi.dll.
The file is part of Internet Explorer 6.0 SP1 (it shows how embedded IE is into Windows!).
It is part of the Cumulative Update for IE6 SP1.
Because of this, the file (and others in IE) are designed for all OSs from 98 to XP.
Therefore, it will check the OS and available DLL exports and run accordingly.
In this case I would not be concerned by DW's report.
0 -
Here's some more:
Windows Utilities
ONGD - FREE - APSoft MemDump 2.0 --- http://www.tssc.de/products/tools/memdump
ONGD - FREE - APSoft VxDView 1.0 --- http://www.tssc.de/products/tools/vxdview
ONGD - FREE - JAM Software TreeSize Free 2.1 --- http://www.jam-software.com/freeware/index.shtml
LAST - FREE - JAM Software FileList 1.6 --- http://www.freeware-archiv.de/g6.php?id=Fi...&mirror=www
ONGD - FREE - JAM Software HeavyLoad 2.3 --- http://www.jam-software.com/freeware/index.shtml
0 -
I had 1GB of RAM using the following settings:
BIOS:
AGP Aperture Size=256MB
SYSTEM.INI:
ConservativeSwapfileUsage=1
MaxPhysPage=40000 (1024MB)
MaxFileCache=393216 (384MB)
Chunksize=2048
MinFileCache=131072 (128MB)
SYSTEM.INI for performance (an advantage of lots of RAM):
DMABufferSize=64
PagingDrive=D: (your fastest drive, or not Windows drive if same speed, or C:)
MinPagingFileSize=1048576 (1024MB - size in KB - MS recommend between RAM and RAM x1.5 - I suggest 1GB for 1GB or more of RAM)
MinSPs=16
KeyBoostTime=0.1
MinTimeSlice=80
RemovableIDE=1
PageBuffers=32
I have now added 512MB to a total of 1.5GB and tried to boot with the same settings...
Windows got as far as initialising the display driver and stopped with random vertical orange bars on the screen...
Windows still let me do a double Ctrl-Alt-Delete reboot to flush the disk cache etc.
So, I changed the following settings based on experience in this and other threads:
SYSTEM.INI:
MaxPhysPage=48000 (1152MB)
MaxFileCache=114688 (112MB)
Chunksize=1024
(MinFileCache undefined)
Windows now got as far as the desktop, but the display driver failed to initialise and so I got Standard VGA...
I then made the following change and everything works now (been working for 24 hours with some reboots for new updates).
BIOS:
AGP Aperture Size=128MB
I have not used the VCACHE patch yet, but then on it's own, Windows would fail with more than 1GB of RAM anyway...
Does anyone know how to get an address allocation map of the Windows system arena?
This way we could find out exactly what is using address space...
Here is a good MS doc that explains the 9x addressing architecture: http://support.microsoft.com/kb/q125691/
The design limit of Windows 95 is 2GB according to http://support.microsoft.com/kb/q181594/
However, Windows 98 and Me are 1GB according to http://support.microsoft.com/kb/304943
The key phrase being "Windows Me and Windows 98 are not designed to handle more than 1 GB of RAM. More than 1 GB can lead to potential system instability."
Go figure! Why would M$ make their newer OSs support less RAM???
Conspiracy theorists would say that M$ were manuvouring users towards 'End-Of-Life' for 9x...
But anyway, what exactly is causing this?
Answer: Windows Virtual Memory Manager (VMM.VXD) - as pointed out by Tihiy in an earlier post.
It loads first after WIN.COM and is the only place where physical RAM is exposed before being virtualised and re-mapped.
Everything else does not care, or know, about all that physical RAM since it's virtualised!
The load order is:
-HIMEM.SYS
-IFSHLP.SYS
-WIN.COM
-VMM.VXD
-SMARTDRV.EXE
-VXD modules and so on.
How to find or determine the flaws in VMM.VXD? - THE Question.
Further reading:
http://www.aumha.org/win4/a/memmgmt.php
http://www.aumha.org/win4/a/resource.htm
http://onlinehelp.bc.ca/tips.htm
Writing Windows VxDs and Device Drivers By Karen Hazzah: http://books.google.com/books?id=F868yPHsA...tsec=frontcover
(Missing Chapter 4 in Preview but otherwise some good reading!)
Over 1GB of Usable Windows RAM - The Windows 9x Great Frontier!
0 -
...back in the days before AutoPatcher, Gape's unofficial
service pack for 98SE had something called a "windows 2000 color scheme" which was more
pleasant than the default (gray) colors I've had since switching to UBCD and AutoPatcher.
...
It should be an OPTION in AP, so we don't have to run Gape's AFTER AP.
...
I totally agree with joe tweaker!
I had Gape's original USP 2.1a installed before I started using AP.
I have the Windows 2000 scheme at the moment. Much nicer.
So, sop, there's another thing to add to AP - Windows 2000 Appearance Scheme as used in Gape's original USP 2.1a.
BTW, have you looked at ASPI Layer 4.71.2?
Have a look: http://www.adaptec.com/en-US/speed/softwar...i_471a2_exe.htm
You can expand the compressed files (.??_) with the Microsoft EXPAND.EXE utility that comes with Windows 2000.
It also comes with Windows XP but will not work in 9x. Obviously you can expand the files in XP.
You will need to rename to add the last character of the extention.
Windows 95-98-98SE-Me - Let the Good Times roll.
0 -
Hi soporific,
I like the install counter and I think it should be included!
I've installed the Dec 2007 RC1. Have not installed RC2 yet...
Mostly went okay.
There were some issues though...
- InfraRecorder update section gave an 'access denied' error when trying to remove the old version.
- The Twain update looped - probably because I already have the updated files...
- The 48BitLBA update looped - I had previous 48bit 4.10.0.2225 installed. I uninstalled so the new 4.10.0.2230 version would install.
- The SYSTEM.ini tweaks menu option gave me an 'out of environment space' error and went back to the main menu.
When I freed up some environment space to work around the error, it correctly detected my RAM as 1.5GB, but used the wrong formula to calculate.
It set MaxFileCache to 262144 which would have killed Windows! - my current (maximum) setting is 114688.
Probably because of this the Chunksize was set as 2048. I use 1024.
When I selected current SYSTEM.INI settings, the Chunksize, MinFileCache, and MaxFileCache did not match my current settings...
- There is something wrong with the Visual Basic menu... There is no official VB6 entry and yet I get this in the log (as mentioned by billygoat):
21:31:44 -- superceeded: -- VBRUN600 (Official Visual Basic 6.0 sp6 Runtime Files)
File: C:\WINDOWS\system\msvbvm60.dll
Current: 6.0.97.98
Attempted: 6.0.97.82
...And now for the BIG one...
BROWSEUI.DLL 6.0.2800.1915 from kb942615 kills my Windows Explorer (failure in EXPLORER.EXE).
The Desktop comes up okay, but anytime I try to open a browse window, it dies...
Now, the catch is that I have EXPLORER.EXE 5.50.4134.100 from Revolutions Pack 7.11.
I expect that the same thing would happen using 98SE2ME with the Me Explorer option installed.
It may or may not work with 98SE EXPLORER.EXE...
I have had to back-date BROWSEUI.DLL to 6.0.2800.1914 from kb939653.
0 -
...
Likewise, if there's a benefit (or no worry) to the newer msvbvm60.dll, why did it appear in the August AP but seems to have been removed in AP October Full?
...
billygoat, there are both the official and the unofficial VB 6 updates.
If they were both selected in August AP, then the files will be at the unofficial versions.
When you run the October AP, the official update says that the msvbvm60.dll file is newer.
This is correct because it is the unofficial version.
There are many updates in AP that have both the official and the unofficial and even some official updates that have some newer files in other official updates...
You will get the same newer file message for some others as well.
soporific, that's a rocking list of updates this time around!
Small error in your change log...
...new: kb927978 - MSXML 4.0 SP2 Update
....
removed: kb925672 - MSXML 4.0 SP2 Update (replaced by kb941833) < should say replaced by kb927978 (above)
...
Rock on soporock!
0 -
...
my dear sir, please check the change log again.
Checked the change log... Sorry... Just being lazy I suppose......14:43:06 -- superceeded: -- kb925672 (MSXML 4.0 SP2 Update)
File: C:\WINDOWS\system\msxml4.dll
Current: 4.20.9848.0
Attempted: 4.20.9839.0
...
14:52:01 -- superceeded: -- VBRUN600 (Official Visual Basic 6.0 sp6 Runtime Files)
File: C:\WINDOWS\system\msvbvm60.dll
Current: 6.0.97.98
Attempted: 6.0.97.82
...
billygoat, msxml4.dll versions higher than 4.20.9841.0 (kb927978) have problems in Windows 9x.
Remove msxml4 from Add/Remove Programs, then delete msxml4.dll from \WINDOWS\SYSTEM and run Auto-Patcher again.
The official Visual Basic 6 files are older than the unofficial update so do not worry about that one.
soporific, the December 2007 Microsoft Root Certificates Update has been released.
0 -
Hey soporific, did you ever replace the dodgy OLEUP update with the corrected one from MDGx? (Since August release)
See here for a memory jogger: http://www.msfn.org/board/Auto-Patcher-Win...566#entry696566
0 -
After you've run Auto-Patcher and got Windows up to date, I suggest you visit Last Versions of Software for Windows 98SE for software, and hardware drivers that are compatible with Windows 98SE.
0 -
Okay, nice tool. Simple but nice.
Windows Utilities
ONGD - FREE - CodeStuff Starter --- http://codestuff.tripod.com/products_starter.html
Drugwash, when I've got time I'll compare the two...
Always good to have constructive input and ideas.
0 -
Okay, here's the dig on kb941833 MSXML4.DLL 4.20.9849.0...
Same problem as previous version 4.20.9848.0.
I used AnVir Task Manager Free to show open DLLs for an application.
Some that opened MSXML4.DLL failed.
No errors, just an empty window with maybe a toolbar...
Roll back MSXML4.DLL to good version and it works...
It is important to determine that an application actually uses MSXML4.DLL since some will use MSXML.DLL, MSXML2.DLL, or MSXML3.DLL only or a combination.
Not good...
Last good version was kb927978 version 4.20.9841.0.
0 -
Another well known app:
Windows Utilities
ONGD - FREE - Dependency Walker --- http://www.dependencywalker.com/
Hey Drugwash,
I think AnVir Task Manager Free is a great tool. The 'Pro' features I don't really need anyway.
I do not start it with Windows and only run it when I need to check out what's going on behind the scenes!
The reason for it's resource and system requirements is because it is a powerful utility.
Sure, their are smaller TMs for older systems too.
0 -
Hi Offler,
Download Dependency Walker from here: http://www.dependencywalker.com/
Open the executable of the problem app or install in DW and it will show you all the DLLs required by the app and also those that are not available.
0
)
Checked the change log... Sorry... Just being lazy I suppose...
Auto-Patcher For Windows 98se (English)
in Windows 9x Member Projects
Posted
Hi soporific,
I have found a problem with AP's detection for the OLEUP install.
I have some software that has online updating. It's worked okay updating for some time.
However, the last update decided that I was running Windows XP SP2 (as everyone does... NOT), and installed XP SP2 OLE files...
As you can imagine, or know, Windows did not like this and most of my start-up apps failed and Explorer became unstable.
So, I manually ran OLEUP from AP and rebooted. Problem gone.
When I ran System File Checker, it showed that OLEAUT32.DLL had changed.
OLEAUT32.DLL was updated from 2.40.4522 to the newer 2.40.4519. Anyone thinking it's a typo see here (post #912).
Getting to the point, what this means, is that AP is not detecting the OLEUP update install correctly since AP said it was already installed, when in fact it was not up to date...
Another small fix needed in AP.