Sonnet 7200 PCI programming - Page 56

Hedeon · 03 September 2017, 23:28

Quote:

Originally Posted by grelbfarlk

Is there some application which starts working after doing this or breaks if it is not done?

No. The original powerpc.library used it to put the gfx memory address range in a BAT to speed up things. It does not work with the sonnet. The sonnet sets the gfx memory by default in a BAT register. No ENV/powerpc stuff is looked at, at the moment.

Hedeon · 03 September 2017, 23:42

Quote:

Originally Posted by trixster

Setting it at 160mhz (4) seems to be absolutely fine. And now setting it at 200mhz (3) also seems to be absolutely ok too, nothing crashing at the moment. How odd.

What happens if you set it to 0? And then what happens if you delete it from ENVARC: ?

Seeing that Spudje also has a 400/1M...hmm..but I can't see anything wrong with the code.

grelbfarlk · 03 September 2017, 23:56

Quote:

Originally Posted by Hedeon

No. The original powerpc.library used it to put the gfx memory address range in a BAT to speed up things. It does not work with the sonnet. The sonnet sets the gfx memory by default in a BAT register. No ENV/powerpc stuff is looked at, at the moment.

You know what we should do is put the original ppc.library in ROM at U1, then we could use all the tools to disable it for more compatibility.

Hedeon · 04 September 2017, 00:11

Just release some ports with no sound, plz thnx.

A shame if it was another two weeks..

trixster · 04 September 2017, 18:29

Quote:

Originally Posted by Hedeon

What happens if you set it to 0? And then what happens if you delete it from ENVARC: ?

Seeing that Spudje also has a 400/1M...hmm..but I can't see anything wrong with the code.

Currently testing #281.

If I remove SetCMemDiv from ENVARC:Sonnet and reboot, then upon running something like Quake2 I will get a crash (hard lockup usually) within about a minute or two.

Setting SetCMemDiv to 3 and everything works perfectly.

Setting SetCMemDiv to 0 and everything so far (fingers crossed) seems to be working perfectly.

Hedeon · 04 September 2017, 21:00

Quote:

Originally Posted by trixster

Currently testing #281.

If I remove SetCMemDiv from ENVARC:Sonnet and reboot, then upon running something like Quake2 I will get a crash (hard lockup usually) within about a minute or two.

Setting SetCMemDiv to 3 and everything works perfectly.

Setting SetCMemDiv to 0 and everything so far (fingers crossed) seems to be working perfectly.

Still not sure what is wrong...could you test 282 283 while removing SetCMemDiv?

trixster · 04 September 2017, 21:20

I'll give #283 a try!

Don't discount the high probability that I'm doing something wrong with my testing, I'm a bit crap at it! User error

if no one else is encountering any issues then it's maybe just me that's the issue

Wrangler · 04 September 2017, 21:43

A couple of updates from me:

I've updated the guide to replace the reference to the WarpOS environment variables with a reference to the Sonnet ones. And I've added some instructions for keeping the library out of libs: and initialising it on demand. I think someone requested that.

@Hedeon: the problem with gearsppc.exe comes from BoingBags3&4 and (I am guessing here) the revised ROM update it installs. Anyway it's something in that collection that is clashing with gearsppc.exe, probably, as you say, down to a lack for proper error checking in gearsppc.exe. Having said that, it works fine on a CSPPC with WarpOS but I guess that's because the same people wrote WarpOS, Warp3D and gearsppc...

trixster · 04 September 2017, 22:17

With #283 if i remove SetCMemDiv from ENVARC:sonnet and reboot, BlizQuake will crash within about 20 seconds of starting the first demo run through. I tried this twice with cold reboots in between.

With SetCMemDiv back in place, following a reboot BlizQuake has been running for the last 50 minutes on demo loops without issue.

The A4000 has been on pretty much continuously now since about 1400 this afternoon so it's about a warm as it's going to get! I'm still running with case lid off and with a fan taking hot air away from the voodoo and the sonnet.

EDIT!

Scratch that, I had SetCMemDiv at 4 during that last 50min test. I've just put it to 3, reset everything and now BlizQuake has crashed within about 15 seconds.

Damn. Told you i was crap at this

200mhz cache on my card unstable? I'll go back to the aminet powerpc.library for a while as that seems to be fine, no crashes to report.

spudje · 04 September 2017, 22:30

Sorry guys, haven't had the time yet to join you in testing SetCMemDiv. I hope to have some time any of the upcoming evenings this week. So do I understand it correctly it's a Sonnet ENVARC (ENVARC:Sonnet/SetCMemDiv), so not Warp3D, Picasso96 or Mediator ENVARC?

Quote:

Originally Posted by Wrangler

A couple of updates from me:
@Hedeon: the problem with gearsppc.exe comes from BoingBags3&4 and (I am guessing here) the revised ROM update it installs. Anyway it's something in that collection that is clashing with gearsppc.exe, probably, as you say, down to a lack for proper error checking in gearsppc.exe. Having said that, it works fine on a CSPPC with WarpOS but I guess that's because the same people wrote WarpOS, Warp3D and gearsppc...

I only have BB1&2 and still have Gears crash on me.

Hedeon · 04 September 2017, 23:28

Quote:

Originally Posted by Wrangler

@Hedeon: the problem with gearsppc.exe comes from BoingBags3&4 and (I am guessing here) the revised ROM update it installs. Anyway it's something in that collection that is clashing with gearsppc.exe, probably, as you say, down to a lack for proper error checking in gearsppc.exe. Having said that, it works fine on a CSPPC with WarpOS but I guess that's because the same people wrote WarpOS, Warp3D and gearsppc...

I've BB3 and 4 installed. Actually in an EEPROM. Albeit i haven't updated since like 0.9f.

Hedeon · 04 September 2017, 23:29

Quote:

Originally Posted by spudje

Sorry guys, haven't had the time yet to join you in testing SetCMemDiv. I hope to have some time any of the upcoming evenings this week. So do I understand it correctly it's a Sonnet ENVARC (ENVARC:Sonnet/SetCMemDiv), so not Warp3D, Picasso96 or Mediator ENVARC?

Yes. Try with ENVARC:Sonnet/SetCMemDiv at 5 first.

Hedeon · 04 September 2017, 23:30

Quote:

Originally Posted by trixster

Damn. Told you i was crap at this

You reported it worked with 281 and the setting at 3 and 0. Was this wrong? How does 283 perform with 0?

grelbfarlk · 05 September 2017, 01:00

Here's a fresh build of 284 with the faster RAM timings-new changes in the library to the PGMAX register seems to increased the WriteB benchmark in Sysspeed by another ~4MB/s to 99.5MB/s for me. No real noticeable improvement in application speed though.

trixster · 05 September 2017, 06:33

Quote:

Originally Posted by Hedeon

You reported it worked with 281 and the setting at 3 and 0. Was this wrong? How does 283 perform with 0?

No, this was correct. 281 with 3 and 0 were ok. I'll try 283 with 0 tonight

trixster · 05 September 2017, 18:04

I've just run 283 with 0 from a cold machine and blizquake has locked up 4 minutes into demo looping.
4 runs without issue
3 locks up after about 20 seconds

281:
3 locks up after about 20 seconds
4 runs without issue
0 seems to run ok so far, no lockups! - this has now been running quake and mame for 1.5hrs with zero issues.

278 locks up after a few minutes!

270 runs without issue

Aminet version runs fine without issue

So today's results for 281 dont match what i saw yesterday with regard to setting 3. And i cant fathom why 0 will work with 281 but not 3. As a result Im not sure we can make of what i'm seeing if no one else is reporting a problem. A peculiarity of my sonnet and system setup?

Off to do more testing.

Wrangler · 05 September 2017, 19:18

Quote:

Originally Posted by spudje

I only have BB1&2 and still have Gears crash on me.

Have you tried fresh install based on the guide? Any joy with that? And does gears_68k work for you?

Wrangler · 05 September 2017, 19:20

Quote:

Originally Posted by Hedeon

I've BB3 and 4 installed. Actually in an EEPROM. Albeit i haven't updated since like 0.9f.

I suspect it's going to be almost impossible to track this down any further because I can't find BoingBags 3 and 4 separately any more to test version 0.9f.

spudje · 05 September 2017, 20:53

Quote:

Originally Posted by Wrangler

Have you tried fresh install based on the guide? Any joy with that? And does gears_68k work for you?

My install is basicly identical to the install in the guide, so I'm not going to do it again. Gears68 and Warptest work fine. ABout to continue my tests.

BTW a small addition to your guide:
The config jumper (labeled SWAP on my mediator) has to be closed if you have either a ZorRAM or BigRAMPlus installed. At least for it was required, see http://eab.abime.net/showpost.php?p=...postcount=1040

Can I simply change the library file to check different versions or is initppc different for each version as well?

Hedeon · 05 September 2017, 21:54

Quote:

Originally Posted by Wrangler

I suspect it's going to be almost impossible to track this down any further because I can't find BoingBags 3 and 4 separately any more to test version 0.9f.

I know it is a lot to ask, but you could manually install bb4 and see which component is the culprit.

04 September 2017, 22:17	#1109
trixster Guru Meditating Join Date: Jun 2014 Location: England Posts: 2,356	With #283 if i remove SetCMemDiv from ENVARC:sonnet and reboot, BlizQuake will crash within about 20 seconds of starting the first demo run through. I tried this twice with cold reboots in between. With SetCMemDiv back in place, following a reboot BlizQuake has been running for the last 50 minutes on demo loops without issue. The A4000 has been on pretty much continuously now since about 1400 this afternoon so it's about a warm as it's going to get! I'm still running with case lid off and with a fan taking hot air away from the voodoo and the sonnet. EDIT! Scratch that, I had SetCMemDiv at 4 during that last 50min test. I've just put it to 3, reset everything and now BlizQuake has crashed within about 15 seconds. Damn. Told you i was crap at this 200mhz cache on my card unstable? I'll go back to the aminet powerpc.library for a while as that seems to be fine, no crashes to report. Last edited by trixster; 04 September 2017 at 22:28.

05 September 2017, 01:00	#1114
grelbfarlk Registered User Join Date: Dec 2015 Location: USA Posts: 2,972	Here's a fresh build of 284 with the faster RAM timings-new changes in the library to the PGMAX register seems to increased the WriteB benchmark in Sysspeed by another ~4MB/s to 99.5MB/s for me. No real noticeable improvement in application speed though. Last edited by grelbfarlk; 27 January 2018 at 01:38.

05 September 2017, 18:04	#1116
trixster Guru Meditating Join Date: Jun 2014 Location: England Posts: 2,356	I've just run 283 with 0 from a cold machine and blizquake has locked up 4 minutes into demo looping. 4 runs without issue 3 locks up after about 20 seconds 281: 3 locks up after about 20 seconds 4 runs without issue 0 seems to run ok so far, no lockups! - this has now been running quake and mame for 1.5hrs with zero issues. 278 locks up after a few minutes! 270 runs without issue Aminet version runs fine without issue So today's results for 281 dont match what i saw yesterday with regard to setting 3. And i cant fathom why 0 will work with 281 but not 3. As a result Im not sure we can make of what i'm seeing if no one else is reporting a problem. A peculiarity of my sonnet and system setup? Off to do more testing. Last edited by trixster; 05 September 2017 at 19:54.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
WANTED: PCI Sound Card VORTEX2 SuperQuard / SQ2500 or Turtlebeach SantaCruz pci card	keropi	MarketPlace	12	15 March 2017 02:48
Wanted:Sonnet Technologies QuadDoubler 50 (Doubler 4000)	kronuz	MarketPlace	0	16 June 2013 00:29
eBay : Sonnet Quaddoubler	alexh	MarketPlace	3	07 May 2013 00:50
Overlay problem on GeForce 7200	Leandro Jardim	support.WinUAE	1	10 August 2010 15:50
Prometheus PCI & Voodoo 3 PCI GFX Card	Slayer	support.Hardware	21	05 September 2006 10:57

04 September 2017, 00:11	#1104
Hedeon Semi-Retired Join Date: Mar 2012 Location: Leiden / The Netherlands Posts: 2,047	Just release some ports with no sound, plz thnx. A shame if it was another two weeks..

04 September 2017, 21:20	#1107
trixster Guru Meditating Join Date: Jun 2014 Location: England Posts: 2,356	I'll give #283 a try! Don't discount the high probability that I'm doing something wrong with my testing, I'm a bit crap at it! User error if no one else is encountering any issues then it's maybe just me that's the issue

04 September 2017, 21:43	#1108
Wrangler Registered User Join Date: Sep 2015 Location: London, UK Posts: 419	A couple of updates from me: I've updated the guide to replace the reference to the WarpOS environment variables with a reference to the Sonnet ones. And I've added some instructions for keeping the library out of libs: and initialising it on demand. I think someone requested that. @Hedeon: the problem with gearsppc.exe comes from BoingBags3&4 and (I am guessing here) the revised ROM update it installs. Anyway it's something in that collection that is clashing with gearsppc.exe, probably, as you say, down to a lack for proper error checking in gearsppc.exe. Having said that, it works fine on a CSPPC with WarpOS but I guess that's because the same people wrote WarpOS, Warp3D and gearsppc...

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)