Because rapidshare...
98 SE SP 3.19 Mar 11, 2013
#681
Posted 29 November 2009 - 06:51 AM
Because rapidshare...
#682
Posted 29 November 2009 - 09:59 AM
#683
Posted 01 December 2009 - 09:53 AM
luluthefirst, on Nov 29 2009, 05:51 AM, said:
Because rapidshare...
All 98 SE SP2 editions are here:
http://www.mdgx.com/web.htm#SPX
Enjoy.
#684
Posted 29 January 2010 - 08:24 PM
#685
Posted 01 April 2010 - 05:24 AM
It concerns the MS update known as "Microsoft Internet Explorer 5 Toolbar Wallpaper" as shown in your Add/Remove Programs list. Otherwise knows as tbwlpapr.exe
One of the little known cute things about it is that the wallpaper you choose for IE can also be applied to Windows Explorer and it really classes the place up a bit but that last part is broke. I'm thinking it ought to be applied and if you don't want it, you can right click on the tabletop and remove or change the wallpaper as you see fit. The original update did NOT include the methodology to apply the wallpaper to Windows Explorer with just this slight alteration in the registry:
from this (IE only)
HKCU,"SOFTWARE\Microsoft\Internet Explorer\Toolbar","BackBitmapIE5",,"%10%\Clouds.bmp"
to these two (both explorers)
HKCU,"SOFTWARE\Microsoft\Internet Explorer\Toolbar","BackBitmapIE5",,"%10%\Clouds.bmp"
HKCU,"SOFTWARE\Microsoft\Internet Explorer\Toolbar","BackBitmapShell",,"%10%\Clouds.bmp"
If you have the clouds.bmp file in your Windows directory where it would be if you had it at all, you will now have that file as wallpaper for both Explorers. You'll have to close all instances and then open new ones to see the change, but no reboot is necessary for this little trick to happen.
We inflict this change by altering toolimg.inf and adding both those lines to both the
[User.AddReg]
[Machine.AddReg]
sections of the toolimg.inf file. We then need to add code to the toolbar.hta file so that it functions to rewrite both those registry locations with updated data according to the added toolbar widget that this update provides to the right click toolbar menu.
We go from this text snippet in the toolbar.hta file:
**************
function writeRegistry() {
//set the HKEY_CLASSES_ROOT values
var strKeyBase = "HKCU\\Software\\Microsoft\\Internet Explorer\\Toolbar\\BackBitmapIE5";
wsho.RegWrite(strKeyBase, txtSkinName.value, "REG_SZ");
strKeyBase = "HKLM\\Software\\Microsoft\\Internet Explorer\\Extensions\\{c23dd370-cb79-11d2-898a-00c04f80a47f}\\UseWinFolder";
wsho.RegWrite(strKeyBase, UseWinPath, "REG_SZ");
alert("Your toolbar has been customized. Close all IE windows, and then restart IE to see your new toolbar.");
window.close();
*************
to this:
function writeRegistry() {
//set the HKEY_CLASSES_ROOT values
var strKeyBase = "HKCU\\Software\\Microsoft\\Internet Explorer\\Toolbar\\BackBitmapIE5";
wsho.RegWrite(strKeyBase, txtSkinName.value, "REG_SZ");
strKeyBase = "HKCU\\Software\\Microsoft\\Internet Explorer\\Toolbar\\BackBitmapShell";
wsho.RegWrite(strKeyBase, txtSkinName.value, "REG_SZ");
strKeyBase = "HKLM\\Software\\Microsoft\\Internet Explorer\\Extensions\\{c23dd370-cb79-11d2-898a-00c04f80a47f}\\UseWinFolder";
wsho.RegWrite(strKeyBase, UseWinPath, "REG_SZ");
alert("Your toolbar has been customized. Close all IE windows, and then restart IE to see your new toolbar.");
window.close();
**************
and now the right click toolbar widget changes the wallpaper on both explorers to what ever you want or back to nothing at all as you see fit. I store my wallpaper widget on the left side of the right click choice device so I don't even see it unless I'm after it. I certainly don't want it on my toolbar cluttering up things when I only use it a couple of times in as many years.
One other "bug" that MS didn't see fit to correct on this update was the improper text used in the zoomin.htm and zoomout.htm files that wind up in the C:\WINDOWS\WEB folder. When you right click an object in IE after you apply this update you will have two added choices. To zoom in or to zoom out. They never worked before, but with this text subtituted for those files they will work correctly from now on.
zoomin.htm
***************
<HTML>
<script LANGUAGE="JavaScript" defer>
var parentwin = external.menuArguments;
var doc = parentwin.document;
var w;
var h;
if ( parentwin.event.srcElement.tagName == "IMG" )
{
h = parentwin.event.srcElement.height * 2;
w = parentwin.event.srcElement.width * 2;
parentwin.event.srcElement.height = h;
parentwin.event.srcElement.width = w;
}
else
alert ("You must right-click on an image to Zoom.");
</SCRIPT>
</HTML>
***************
and zoomout.htm
**************
<HTML>
<script LANGUAGE="JavaScript" defer>
var parentwin = external.menuArguments;
var doc = parentwin.document;
var w;
var h;
if ( parentwin.event.srcElement.tagName == "IMG" )
{
h = parentwin.event.srcElement.height / 2;
w = parentwin.event.srcElement.width / 2;
parentwin.event.srcElement.height = h;
parentwin.event.srcElement.width = w;
}
else
alert ("You must right-click on an image to Zoom.");
</SCRIPT>
</HTML>
***************
The difference in case you don't spot it right off is times 2 or divide by 2. You can't just copy these files to the named location and expect them to work. They only work with the update applied and the original files replaced with these ones. I suspect it's a fleshing out of shell32.dll file's functions that were placed in there with the "new" IE5 but never used before without this update applied.
So it's a sweet little toy that I think ought to used more especially in it's fixed form. When I work on a machine that DOESN'T have the wallpaper - I really notice it...
#686
Posted 01 April 2010 - 07:21 AM
You don't have to do it that way. What you can do instead is just install the different aspi files and then set the SetupProgramRan key to a value greater than zero and at the next bootup Windows will run a NEW checksum entry on the files you just installed and then start using that information to "protect" those listed dll files from ever changing again. This is all it takes:
HKLM,"System\CurrentControlSet\Control\Shutdown","SetupProgramRan",0x00010001,01,00,00,00
and a reboot.
The SetupProgramRan key causes this behavior but I haven't figured out yet how to do the same thing over in the CheckVerDLLs list. I'd love to know how to add one in there and have it calculate it's own binary string entry in a similar manner to the WarnVerDLLs list. Somewhere, somehow it sure enough happens though.
#687
Posted 06 June 2010 - 11:16 AM
for the Czech Republic. I need help as
wrap all the translated files into. CAB and
final installer. I can not so much English
perhaps you will understand
#688
Posted 06 June 2010 - 02:24 PM
Ricrdsson, on 06 June 2010 - 11:16 AM, said:
for the Czech Republic. I need help as
wrap all the translated files into. CAB and
final installer. I can not so much English
perhaps you will understand
Have you tried winpack.org ?
Also search this forum for "sp2 localization". You will find many posts by Petr like Localization of SP 2.0
#689
Posted 07 June 2010 - 11:37 AM
Download here: ricrdsson.ic.cz/nsp.html
This post has been edited by Ricrdsson: 13 June 2010 - 03:59 AM
#690
Posted 10 June 2010 - 11:03 AM
Sorry, Final Version?
#691
Posted 18 June 2010 - 06:37 PM
can someone pick up where he left off @?
#692
Posted 20 June 2010 - 08:18 AM
Ricrdsson, on 07 June 2010 - 11:37 AM, said:
I contacted Ricrdsson, whole project nSP 3.0 CS it's now guest on winpack.org.
#693
Posted 27 July 2010 - 12:35 AM
p.s. Project is alive or not?
#694
Posted 28 July 2010 - 12:59 PM
prowler, on 27 July 2010 - 12:35 AM, said:
p.s. Project is alive or not?
MDAC is an optional component, and Gape included only necessary/essential components in the SP.
MDAC can be installed [separately] from Maximus-Decim's package (MDDACU 2.0), updated March 2010:
http://www.msfn.org/...showtopic=93448
or by hand [separate components + updates] at my site, where you can also find links for MDDACU 2.0:
http://www.mdgx.com/add.htm#DAC
2. We haven't heard from Gape in a long time. :-(
I've also been asked to take over this project, and I recommended erpdude8 as a better choice [he has experience with 98FE SP2 + 95OSR2 SP1, which are similar].
So I guess it's safe to assume Gape may not come back to update the SP, unless some1 knows different.
HTH
#695
Posted 30 July 2010 - 01:53 AM
Philco, on 20 June 2010 - 08:18 AM, said:
Ricrdsson, on 07 June 2010 - 11:37 AM, said:
I contacted Ricrdsson, whole project nSP 3.0 CS it's now guest on winpack.org.
98 SE SP2 3.0 Beta 4 Test [20.9 MB, Czech]:
http://www.mdgx.com/spx/SP30B4CZ.EXE
More info (Czech):
http://www.winpack.org/
HTH
#696
Posted 06 August 2010 - 03:03 PM
In brief, if you replace IO.SYS with Microsoft's fixed version (included in all these 98 SE Service Packs since at least v1.6.2, I believe), then SCANREG.EXE will think your registry is screwed up, replace it with a backup, and reboot. To prevent this from happening every time you boot (which would result in a loop), the service packs just turn off running SCANREG.EXE at boot. (SCANREGW.EXE, the Windows version, still runs and backs up your registry once a day.)
Does anyone know why this happens? The fix to IO.SYS supposedly had nothing to do with accessing large files like the registry. I thought it was just supposed to handle disk errors better.
That's the only concern I have with the service pack so far. It'd be nice if both disk error handling and SCANREG.EXE worked correctly!
#697
Posted 17 September 2010 - 06:08 AM
Refuses to boot (bootlog indicates it gets stuck initializing TCP/IP) on my Presario 3020 desktop. 2.1a works fine on this machine.
#698
Posted 03 October 2010 - 05:30 PM
I am wanting to use the "slip stream" method given in the readme file. As explained this will only apply the updates which replace already existing files - not the updates that give new files. So I am wondering what updates will I need to apply the "old fashioned" way, as the readme doesn't list either the updates that work this was nor the updates that don't.
Thanks in advance.
#699
Posted 06 October 2010 - 05:21 PM
Mathwiz, on 06 August 2010 - 03:03 PM, said:
In brief, if you replace IO.SYS with Microsoft's fixed version (included in all these 98 SE Service Packs since at least v1.6.2, I believe), then SCANREG.EXE will think your registry is screwed up, replace it with a backup, and reboot. To prevent this from happening every time you boot (which would result in a loop), the service packs just turn off running SCANREG.EXE at boot. (SCANREGW.EXE, the Windows version, still runs and backs up your registry once a day.)
Does anyone know why this happens? The fix to IO.SYS supposedly had nothing to do with accessing large files like the registry. I thought it was just supposed to handle disk errors better.
That's the only concern I have with the service pack so far. It'd be nice if both disk error handling and SCANREG.EXE worked correctly!
IO.SYS "tells" the OS to scan + backup the registry by running this command:
SCANREG /FIX
during the native DOS part of the boot process (before Windows GUI loads).
More scanreg info:
http://www.mdgx.com/98-1.htm#SCANREG98
And this happens because that particular IO.SYS update (WINBOOT.SYS = renamed to IO.SYS and installed in C:\ root by MSKB Q311561 fix) is somehow broken, and sends the OS boot process into a loop [?], if SystemReg=1, which is the default setting if no SystemReg= line exists in MSDOS.SYS (+ WINBOOT.INI, if any) under the [Options] section.
WINBOOT.INI guide:
http://www.mdgx.com/newtip16.htm#WBINI
HTH
#700
Posted 08 October 2010 - 02:16 PM
First and foremost this is the app I need compatibility with, followed by KernelEx.
Also...
If it does work with 98lite, does anyone know if I can slip-stream in just the updates, and do a "clean install" with 98lite? Will the newer slip-streamed files get copied over by 98lite?
-Edit-
Actually, yes it does work with 98lite. 98lite copied over all of the updated files
Problem is that even with a original (non-98lited) install, this SP creates all sorts of blue-screen crashes, and errors.
Not worth using, especially if it messes with my ability to use disc burning software.
This post has been edited by HardDriv'n: 10 October 2010 - 08:38 PM



Help

Back to top









