Perhaps you try the latest Beta BIOS 1006.002
https://www.asus.com/supportonly/TUV4X/HelpDesk_BIOS/

Thank you for the answear.
I will try this beta version!

But use a stable platform to program the flash chip.

yes this is the real challenge because for now I have to do all manually. This PC cannot surf the internet (and I don't want), has no OS installed and I have no other PC (only at work).
For sure i will use the stable frequency of the CPU then we will see 😁

Welcome to the late 90's (and early 00's).

At least you have not landed in a time where you would have needed to dialup to a overseas BBS.

Disruptor wrote on 2022-09-26, 22:10:

Welcome to the late 90's (and early 00's).

At least you have not landed in a time where you would have needed to dialup to a overseas BBS.

Yes and No 😁 Because i'm 36 years old. I had my first PC when I was 6 years old thanks to my father that bought to me a Philips MSX (I didn’t understand anything I just played). My first modem was a 56k and I had always followed the "media" building 2 or 3 PC. Surprisingly I did't deal with some kind of errors like this and it was a luck!

Disruptor wrote on 2022-09-26, 17:08:

Perhaps you try the latest Beta BIOS 1006.002
https://www.asus.com/supportonly/TUV4X/HelpDesk_BIOS/

I worked! Now the system doesn't give the error.
But I cannot understand why the system doesn't boot with CPU clock set to 1,4 ghz...
I have to set it to 1050 Mhz

From your description earlier. It sounds like maybe your problem is your ram.

Do you or anyone you know have a big pile of ram to try on it? Sometimes very specific sticks are the key to making it all work.

Sphere478 wrote on 2022-10-08, 07:41:

From your description earlier. It sounds like maybe your problem is your ram.

Do you or anyone you know have a big pile of ram to try on it? Sometimes very specific sticks are the key to making it all work.

You got the point.
The ram is new and if use less than 1 GB than the CPU goes without problems in 1.4 Ghz.
I have to be more precise: the system boots, POST goes ok but then when try to load the OS it hangs showing the "_" blinking..

Now I have 1,5 Gb of RAM with 4 modules 512x2 + 256x2
The RAM are:
- 512: SDRAM 133mhz pc133 168-pin cl3 kvr133x72rc3/512 (3.3V)
-256: SDRAM 133mhz pc133 168-pin cl3 kvr133x72rc3/256 (3.3 V)

I will try to ask my friends if they have old ram but I'm the only one of us that loves retro hardware 🤣

I can't really understand...

I have experienced similar problems and it turned out to be excess load on RAM bus, sticks with chips on both sides were simply too much for the chipset to handle properly and errors started to happen even though sticks themselves were good and tested perfect individually.

It sucks, but sometimes best ram
Isn’t max ram.

Try 256 x 4

Try dual and single sided sticks.

single sided may work if overloading is the problem, dual may work if density is the problem.

As far as I know you can’t use more than 512MB of RAM with Windows 98 unless you manually change some registry settings. Not sure if the hang at boot is what happens in this case or not.

Anyway, you don’t really need more than 512MB for Windows 98 unless you know for a fact that you do or you just want to.

Oh yeah^ forgot about that. Does ME have that problem also?

Sphere478 wrote on 2022-10-08, 09:30:

Oh yeah^ forgot about that. Does ME have that problem also?

Yes. But the symptoms may differ. Attached the Microsoft fix.

Tiido wrote on 2022-10-08, 08:31:

I have experienced similar problems and it turned out to be excess load on RAM bus, sticks with chips on both sides were simply too much for the chipset to handle properly and errors started to happen even though sticks themselves were good and tested perfect individually.

An update, I tried one module of 512, that has chips on both sides and 1,4 Ghz. It doesn't start 🙁
This is new because I remeber that the first time I tied, it did't halt on boot.... maybe I was wrong.
The problem seems to be something else..

TrueVegas wrote on 2022-10-10, 21:10:

An update, I tried one module of 512, that has chips on both sides and 1,4 Ghz. It doesn't start :-( This is new because I remeb […]
Show full quote

Tiido wrote on 2022-10-08, 08:31:

I have experienced similar problems and it turned out to be excess load on RAM bus, sticks with chips on both sides were simply too much for the chipset to handle properly and errors started to happen even though sticks themselves were good and tested perfect individually.

An update, I tried one module of 512, that has chips on both sides and 1,4 Ghz. It doesn't start 🙁
This is new because I remeber that the first time I tied, it did't halt on boot.... maybe I was wrong.
The problem seems to be something else..

I know I'm super late to the party, but just for documentation purposes you may try the following:

Go to the bios, find the option "CPU-DRAM Back-Back Transaction" and set it to DISABLED.

Then see if that solved the issue.

Taken from here: https://forums.tomshardware.com/threads/tuv4x … st-post.423319/

Am386DX-40 wrote on 2023-07-25, 18:41:

I know I'm super late to the party, but just for documentation purposes you may try the following: […]
Show full quote

TrueVegas wrote on 2022-10-10, 21:10:

An update, I tried one module of 512, that has chips on both sides and 1,4 Ghz. It doesn't start :-( This is new because I remeb […]
Show full quote

Tiido wrote on 2022-10-08, 08:31:

I have experienced similar problems and it turned out to be excess load on RAM bus, sticks with chips on both sides were simply too much for the chipset to handle properly and errors started to happen even though sticks themselves were good and tested perfect individually.

An update, I tried one module of 512, that has chips on both sides and 1,4 Ghz. It doesn't start 🙁
This is new because I remeber that the first time I tied, it did't halt on boot.... maybe I was wrong.
The problem seems to be something else..

I know I'm super late to the party, but just for documentation purposes you may try the following:

Go to the bios, find the option "CPU-DRAM Back-Back Transaction" and set it to DISABLED.

Then see if that solved the issue.

Taken from here: https://forums.tomshardware.com/threads/tuv4x … st-post.423319/

It's never too late 😁. I abandoned the project but now with this information I will try!! Thank you for the suggestion!

Cool, hope you succeed.