[maninabox]

[OT]

x Petr

try this link:

http://www.mrufer.ch...tualatin_e.html

or this:

http://digilander.li...o/Tua_BX_41.htm

the process is the same for more bx motherboard.

I have abit bx133 with celeron tualatin 1100(100fsb) overclocked 1463(133fsb).
The problem is the agp divisor that at 133 is only 2/3. You need a video card capable to go at 89mhz fsb if you want use p3 tualatin 133 or overclocked celeron (normally all gf3, some gf2 and 8500) or a pci video card.

This post has been edited by maninabox: 22 June 2005 - 09:18 AM

[krick]

Petr, on Jun 21 2005, 11:36 PM, said:

I have several Intel 440BX based boards and I always thought that they don't support Tualation processor?
<{POST_SNAPBACK}>

With the proper adapter, it can work...

Socket 370 tualatin adapter:
http://www.strattonc...370adcpuup.html

Slot 1 tualatin adapter:
http://www.strattonc...ot1-fcpga2.html

Officially, my Abit BM6 motherboard will only support non-coppermine CPUs up to 600MHz.

Notes from the QT bios revision: "Supports 1.5V (cB0 stepping) Celeron 566(66) and 600(66) MHz CPUs. CC0 and newer stepping Celeron CPUs are not supported."

However with a bit of work, I managed to run a 1.1GHz coppermine chip on it...
http://www.3feetunder.com/krick/bm6/

And I later used one of the Socket 370 adapters above to run a 1.4GHz tualatin CPU in it.

[MDGx]

randiroo76073, on Jun 21 2005, 10:58 PM, said:

I still can't figure out why my sound drivers get kicked out & won't reinstall, no I'm not using opt-3, just 1&2. I'm on my 3rd clean install, have all hrdwr drivers in stalled & am ready to install SP2.0.1. Have printout of 982ME Readme & adhere strictly to it on install.  Is there some way to turn off this Digital Signature checker thing in 982ME???

Digital signature is a WinME "feature" [a.k.a. MS WQHL Certification program], but should not normally interfere with driver installation.
If you see an option [Advanced] to turn it off from the dialog box, please do so. More info [scroll down to "Windows Millennium Edition policy" title]:
http://winqual.microsoft.com/help/use_help...efits_help.aspx
The dig sig nag box does not appear at all on my PC, but I must have had disabled it a long time ago.
If u still get such nagging dialogs after doing this, open the respective driver INF file(s) in Notepad and disable [comment, remark] the line that says something like:

CatalogFile=XXXXX.CAT

with a semicolon in front of it, like this:

; CatalogFile=XXXXX.CAT

Save the modified INFs, and then (re)install the respective driver(s).
U can also delete all *.CAT files from the respective driver directory.
This should completely disable that nag box.

Hope this helps.

[randiroo76073]

Thnx MGDx, just got in from mowin, pop a cold 1 & will mod file Will post back later

[MDGx]

PsycoUnc, on Jun 21 2005, 11:02 PM, said:

-MDGx:  ? why did u disable systray?  -is that a performance/stability issue, or just personal preference?

As I said, only because the mouse cursor was spinning for 15-20 seconds right after the UI loaded.
After disabling systray and rebooting, the 15-20 sec spinning cursor went away.

[MDGx]

Petr, on Jun 21 2005, 11:36 PM, said:

MDGx, on Jun 22 2005, 04:52 AM, said:

I tested this on my old PC:
Intel Pentium III Tualatin 1.3 GHz CPU overclocked at 1.4 GHz
Intel 440BX PCI/AGP chipset
Abit BE6-II 2.0 RAID mobo
<{POST_SNAPBACK}>

Hi MDGx, one off-topic question - how you managed to use Tualatin processor on this mobo? Abit states at http://www.abit-usa....s.php?model=119
(Please mention: This board does not support Tualatin core P!!!/Celeron processors.

I have several Intel 440BX based boards and I always thought that they don't support Tualation processor?

Petr

Actually quite simple, I bought a PowerLeap PL-IP3 Slot 1 Tualatin P3 Celeron adapter:
http://www.powerleap.com/PL-iP3T.jsp
which has its own voltage regulator.
Way back then, that was the only way [short of using a soldering gun to mod the VR on the back of the motherboard PCB] to upgrade an Abit slot 1 P3 mobo beyond the 700 MHz P3 slot 1 CPU, unless u use a "slot-ket" adapter, but a primitive slot-ket only supports P3 CPUs up to 1.1 GHz [probably similar to the procedure u used to upgrade to 1.1 GHz].
The last slot 1 P3 CPU made by Intel was the 700E MHz "Coppermine" if memory serves.
More details here [feel free to look around on this page to see my old PC specs]:
http://www.mdgx.com/pc.htm#CPU

This post has been edited by MDGx: 22 June 2005 - 06:25 PM

[randiroo76073]

Great Googliotomy, used 06-21-05 98se2ME ver[b4 was 06-18-05 ver]] no probs with sound drivers Now on the road to rest of rat killin
Have a great week/weekend MGDx

[Eck]

Regarding Randiroo76073's Soundcard driver install problem, I had the same thing happen to me when I was installing the Creative Audigy 2 ZS drivers on my Sblive5.1. Without 98SE2ME this works fine as long as you use the latest ctcomp.exe patch over at driverheaven.

With 98SE2ME, that unsigned driver nag greys out the Advanced box so you can't go in there and tell Windows to ask instead of prevent unsigned drivers from installing. The driver was impossible to install because of this.

I tried using SystemPolicyEditor, but that does not effect the Windows Me driver verification from not allowing the install. That only effects 98SE's driver verification manager. It is set by default to allow all drivers. If I set it to ask, it will ask at the very beginning of the driver installation, but the Windows Me one will still pop up when the actual driver installation is ready to activate the driver. And on the soundcard driver the Advanced box it greyed out. I did successfully install an unsigned driver for another device when the Advanced box was selectable! It only greyed it out for the soundcard driver. On the other device (forget what it was) I clicked the Advanced and chose "Ask" and everything proceeded as it would on Windows Me.

So the only solution to try is changing the inf to ; out the catalog? Is the catalog unimportant?

As you know I using a different card right now so I can't test this. I'm interested to see whether randiroo76073 is successful when he ;'s out the catalog file.

Perhaps this is something that can be left out of 98SE2ME? Are there certain files that activate the Windows Me driver verification check? The 98SE driver verification tool is still there as it popped up when I told System Policy Editor to use it. It will perform the function you set in System Policy Editor or the default "install all" if you leave it as default. However, the Windows Me one ignores the System Policy Editor. It seems we have an extra Driver Verifier that we can really do without.

Edit - Oh. I just noticed that he installed them fine with the later 98SE2ME. Perhaps this is related to the problem we fixed with my USB Modem drivers. Hmmm, maybe things can be left alone then. It does seem that it might be better to just have the 98SE Driver Verifier there though. This way System Policy Editor can still control it. Unless there is something buggy about it that the Windows Me files do better?

This post has been edited by Eck: 23 June 2005 - 01:23 AM

[Eck]

Oops, my internet bugged out somehow and I had the post uploaded twice. Deleted the redundancy! Sorry.

This post has been edited by Eck: 23 June 2005 - 01:18 AM

[tk323]

Hi there. I'm a new poster. I'd like to say first off, thank you to all the people including MDGx and others who have contributed to the exciting program 98SE2ME. It was refreshing to try it and experience a whole new look to Windows 98SE and its usage. I have since reverted back to regular windows though, because there were some problems and I wanted to eliminate as many variables as I could to troubleshoot. I wanted to ask anyone who has knowledge regarding 98SE2ME a question pertaining to my present problem. It seems that for some time now, I've been unable to access MS-DOS from within Windows. I first noticed when I tried to install 98SE2ME that the PIF extension for the file wasn't recognized by Windows. Instead I used a BAT file I believe that was in the file folder for the program. After 98SE2ME was installed, at some point, I realized that my MS-DOS prompt icon was missing from my start menu. It could still be accessed from the run command, after I searched online for solutions and workarounds.
In any case, after some time, I reverted back to the old 98SE config, and also uninstalled the 98se service pack(which I had installed before 98SE2ME), and a few days ago, when trying to enter MS-DOS mode from the shutdown menu, Windows said 'access to specified file or device(EXIT TO DOS.PIF) denied'. I have since seen that I cannot access MS-DOS from the run command either, with COMMAND.COM, and now REGEDIT doesn't work either. I tried the POLEDIT program, and under DEFAULT USER, I found that both regedit and ms-dos were unabled. But after unchecking themand rebooting, the system still is the same, ie. won't recognize pif files, allow access to regedit or command.com(however i can still open REGEDIT if I click on it in Explorer). After rebooting, the poledit program still has all options clear(nothing disabled), but I think there is something in my registry that either I damaged myself, or a program has. It just seems like it has gone from minor to progressively worse. I will try to do a boot-up without the registry enabled to see if that makes a change, because I've already replaced the woa386.mod file, as well as one other that Microsoft lists as the main causes for MS-DOS problems. If anyone knows of any causes of this, or of how to make DOS work properly again, the info would be much appreciated, as I haven't been successful so far in finding a solution.

Good luck with the continued progress and keep on truckin'!

[randiroo76073]

Some further good news on my install, all prgms[3rd party] that load at startup now reinstalled[11], my time from click the restart OK to fully loaded desktop went from "1 min 33 sec"[w/just sp2] to "57 sec" w/98se2ME[opt 1] installed Quite an improvement I'd say! The only time I get to see the new shutdown logo is if I do shutdown Nary a prob so far

[tk323]

Update:

After booting Windows with no registry loaded, the problem with accessing MS-DOS persists. I assume this means that it is a bad file(s) or some incorrect setting. AVG and ad-aware turned up no errors either, so now I'm left wondering what kind of registry tweaks I did in the past that may have triggered this problem. On the net, I read something about incorrect video IRQ's sometimes cause conflict with the MS-DOS ones. I did update the VIA chipset/bus a while back. I can't uninstall them though because the the registry was restored from an older version once and some of the add/remove entries are no longer there. Fuzz. I wish there was some way to reinstall/replace only some files and not the whole windows directory. java script:emoticon('')
smilie

[PsycoUnc]

MDGx, on Jun 22 2005, 07:58 PM, said:

As I said, only because the mouse cursor was spinning for 15-20 seconds right after the UI loaded.
After disabling systray and rebooting, the 15-20 sec spinning cursor went away.

-yes, but why would systray do that? the mouse icon in systray? can't just the icon be disabled? or are there inherent probs w/systray itself?

[PsycoUnc]

randiroo76073, on Jun 23 2005, 04:56 PM, said:

Some further good news on my install, all prgms[3rd party] that load at startup now reinstalled[11], my time from click the restart OK to fully loaded desktop went from "1 min 33 sec"[w/just sp2] to "57 sec" w/98se2ME[opt 1] installed    Quite an improvement I'd say! The only time I get to see the new shutdown logo is if I do shutdown
<{POST_SNAPBACK}>

-yeah, my total boot time is down to 42 secs! niiiice... (celeron 1.8ghz) -mine was around 1 minute, then I saw/tried that MDGx tip "kill TapeDetect in registry", and that shaved 20 secs off! ALL PRAISE MDGX, AGAIN...

[PsycoUnc]

tk323, on Jun 23 2005, 07:12 PM, said:

Update:

After booting Windows with no registry loaded, the problem with accessing MS-DOS persists...
<{POST_SNAPBACK}>

-have ya tried the tweaker X-SETUP, for the Enable DOS box/regedit? GREAT prog... but be sure to get the slightly older 6.6 (FREE) version, mdgx has a link for it... maybe it will succeed where your other tweaker didn't... -also, any chance some security software is cranked up a bit too high? Preventing those functions?

[MDGx]

randiroo76073, on Jun 22 2005, 08:26 PM, said:

Great Googliotomy, used 06-21-05 98se2ME ver[b4 was 06-18-05 ver]] no probs with sound drivers  Now on the road to rest of rat killin
Have a great week/weekend MGDx

Glad it all worked well in the end.

[MDGx]

Eck, on Jun 23 2005, 01:16 AM, said:

Edit - Oh.  I just noticed that he installed them fine with the later 98SE2ME.  Perhaps this is related to the problem we fixed with my USB Modem drivers.  Hmmm, maybe things can be left alone then.  It does seem that it might be better to just have the 98SE Driver Verifier there though.  This way System Policy Editor can still control it.  Unless there is something buggy about it that the Windows Me files do better?

I didn't see any of these errors, and can't test these configurations, so I'll have to trust you guys that it [finally] worked ok on your computers.

[MDGx]

tk323, on Jun 23 2005, 05:15 AM, said:

Hi there. I'm a new poster. I'd like to say first off, thank you to all the people including MDGx and others who have contributed to the exciting program 98SE2ME. It was refreshing to try it and experience a whole new look to Windows 98SE and its usage. I have since reverted back to regular windows though, because there were some problems and I wanted to eliminate as many variables as I could to troubleshoot. I wanted to ask anyone who has knowledge regarding 98SE2ME a question pertaining to my present problem. It seems that for some time now, I've been unable to access MS-DOS from within Windows. I first noticed when I tried to install 98SE2ME that the PIF extension for the file wasn't recognized by Windows. Instead I used a BAT file I believe that was in the file folder for the program. After 98SE2ME was installed, at some point, I realized that my MS-DOS prompt icon was missing from my start menu. It could still be accessed from the run command, after I searched online for solutions and workarounds.
In any case, after some time, I reverted back to the old 98SE config, and also uninstalled the 98se service pack(which I had installed before 98SE2ME), and a few days ago, when trying to enter MS-DOS mode from the shutdown menu, Windows said 'access to specified file or device(EXIT TO DOS.PIF) denied'. I have since seen that I cannot access MS-DOS from the run command either, with COMMAND.COM, and now REGEDIT doesn't work either. I tried the POLEDIT program, and under DEFAULT USER, I found that both regedit and ms-dos were unabled. But after unchecking themand rebooting, the system still is the same, ie. won't recognize pif files, allow access to regedit or command.com(however i can still open REGEDIT if I click on it in Explorer). After rebooting, the poledit program still has all options clear(nothing disabled), but I think there is something in my registry that either I damaged myself, or a program has. It just seems like it has gone from minor to progressively worse. I will try to do a boot-up without the registry enabled to see if that makes a change, because I've already replaced the woa386.mod file, as well as one other that Microsoft lists as the main causes for MS-DOS problems. If anyone knows of any causes of this, or of how to make DOS work properly again, the info would be much appreciated, as I haven't been successful so far in finding a solution. 

Good luck with the continued progress and keep on truckin'!

Hi tk323, and welcome to MSFN forums.

Sounds like you have been using some other program to modify security settings.
98SE2ME does not touch security settings.

To properly use 98SE2ME, please read READ1ST.TXT before replacing any files:
READ1ST.TXT
and also see the list of system files which should *never* be replaced:
http://www.mdgx.com/98-5.htm#NEVER

That's a big no-no: WINOA386.MOD should *not* be replaced.
The only version that works with Windows 98 SE is the 1 that installs from the 98 SE setup CD [build 4.10.2222].
If u do, DOS box mode will be either disabled or messed up, and there is a chance your OS will lock up.

I have a bunch of DOS tricks + guides at my site. Please see this page which contains the entire list:
http://www.mdgx.com/newtip.htm
U can find more info in these text files: MEMORY.TXT, MYTIPS95.TXT, REGIONS.TXT, EMM386.TXT, all part of W95-11D.EXE [freeware for non profit use]:
http://www.mdgx.com/95.htm
All online tips are also included in the text files from W95-11D.EXE if u wish to read offline.
It's a lot of reading, but u may find what u need.

Complete list of Registry keys + values for security permissions:
http://www.mdgx.com/...p9.htm#RESTRICT
System + Registry tweakers [99.99% free(ware)]:
http://www.mdgx.com/toy.htm#SYS

Hope this helps.

And thanks a bunch for your kind appreciation.

[MDGx]

randiroo76073, on Jun 23 2005, 02:56 PM, said:

Some further good news on my install, all prgms[3rd party] that load at startup now reinstalled[11], my time from click the restart OK to fully loaded desktop went from "1 min 33 sec"[w/just sp2] to "57 sec" w/98se2ME[opt 1] installed. Quite an improvement I'd say! The only time I get to see the new shutdown logo is if I do shutdown  Nary a prob so far 

Good news.

If u want to see your boot logo [even if animated] from within Windows, get the XrX logo screen saver [shareware]:
http://www.xrx.ca/lo...index.htm#Saver

Hope this helps.

[randiroo76073]

MGDx not complaining about no sd logo, thats great! When clk "OK" it goes blink to boot screen, figure that shaves seconds off reboot, am now gonna see what can be shaved off backkend PsycoUnc's got me beat by 15 sec