win98 on a p4t-e ?
Now, that my scope rig finally got a new home, I'm amazed about the drawing performance .. it is sooo sloooooow.
The windows and mouse always keep sticking to their positions, when working in scope or DP. The latency between touching, dragging and actually moving the windows is unaccaptable, especially when moving between two screens.
On my old (unfortunately just died) tusl-2 with a p3-600 the drawing speed was fine, so I suspect, it is either the mobo architecture or the OS. As I can't change the hardware right now, my question is, if somebody already used Win98 on a p4t-e with a PIV and if it is actually possible ?
Thanks in advance,
Wolfgang
<font size=-1>[ This Message was edited by: wolf on 2005-10-04 01:07 ]</font>
The windows and mouse always keep sticking to their positions, when working in scope or DP. The latency between touching, dragging and actually moving the windows is unaccaptable, especially when moving between two screens.
On my old (unfortunately just died) tusl-2 with a p3-600 the drawing speed was fine, so I suspect, it is either the mobo architecture or the OS. As I can't change the hardware right now, my question is, if somebody already used Win98 on a p4t-e with a PIV and if it is actually possible ?
Thanks in advance,
Wolfgang
<font size=-1>[ This Message was edited by: wolf on 2005-10-04 01:07 ]</font>
should work with Intel chipset drivers, but I would not recommend. I have XT here with a P3B+750P3- fast, no problem, so: It's not the OS. Must be something with your config. I wouldn't be surprised if you'd eventually run into the same prob with 98, then it's definitely a hardware thing, but before you do that, tell us more about your cards, IRQ etc...
-
- Posts: 334
- Joined: Thu Sep 23, 2004 4:00 pm
- Location: Netherlands
Hi Wolf,
I'm still running Scope on my "old" PT4-E on winXP these days!
But I was using Scope 4 years ago running on windows 98, and it was working fine as well. So I know it's possible to run scope successfully on a win 98 platform (allthough it was version 3.1c) on a P4T-E motherboard.
But with XP it runs just as smooth, or even smoother than ever. I can't even remember a crash or hangup from Scope since I'm running on XP. So for me there is no reason going back
cheers
I'm still running Scope on my "old" PT4-E on winXP these days!
But I was using Scope 4 years ago running on windows 98, and it was working fine as well. So I know it's possible to run scope successfully on a win 98 platform (allthough it was version 3.1c) on a P4T-E motherboard.
But with XP it runs just as smooth, or even smoother than ever. I can't even remember a crash or hangup from Scope since I'm running on XP. So for me there is no reason going back

cheers
Thanks for the answers !
I don't think, Win98 is a good idea for a p4 as well, but this seemed one of the causes .. all drivers are uptodate.
to the config:
All three cards are on different IRQs, one shared it with an USB controller, which I disabled (didn't lead to better response). The system is configured as "ACPI-Uniproc.-PC" (I always forget to hit that F6 key while the initial installation).
Graphic card is a matrox 550 dual screen (busmastering off). It is mostly the 2nd screen, which has that slow response ..
I always frightened the situation having to move my scope rig to a new box .. brrr .. everything worked so smoothly.
Seems I have to reinstall the OS to get a Standard-PC config, so the BIOS settings have an influence. Problem beside the time is, that there's also a network card and a rme hdsp sitting in the box, which might limit the available IRQs in standard config.
ChampionSound:
I don't have any problem with scope itself, it's just the interaction/graphic response (which comes into play in DP especially and never was an issue on Win98).
Are you using standard pc or acpi as basic OS config ?
I don't think, Win98 is a good idea for a p4 as well, but this seemed one of the causes .. all drivers are uptodate.
to the config:
All three cards are on different IRQs, one shared it with an USB controller, which I disabled (didn't lead to better response). The system is configured as "ACPI-Uniproc.-PC" (I always forget to hit that F6 key while the initial installation).
Graphic card is a matrox 550 dual screen (busmastering off). It is mostly the 2nd screen, which has that slow response ..
I always frightened the situation having to move my scope rig to a new box .. brrr .. everything worked so smoothly.
Seems I have to reinstall the OS to get a Standard-PC config, so the BIOS settings have an influence. Problem beside the time is, that there's also a network card and a rme hdsp sitting in the box, which might limit the available IRQs in standard config.
ChampionSound:
I don't have any problem with scope itself, it's just the interaction/graphic response (which comes into play in DP especially and never was an issue on Win98).
Are you using standard pc or acpi as basic OS config ?
-
- Posts: 334
- Joined: Thu Sep 23, 2004 4:00 pm
- Location: Netherlands
I never changed/tweaked any other settings in the BIOS or what so ever because of my lack of knowledge, but fortunately for me everything works just fine.
I remember I installed the ASPI driver that was recommended to install when running SFP on XP. I don't have that much technical knowledge, I don't even know how to check my system if my PC is configured as ACPI, or basic PC configuration. If you can tell me, I'm willing to check it for you. I hope I can help..
cheers
I remember I installed the ASPI driver that was recommended to install when running SFP on XP. I don't have that much technical knowledge, I don't even know how to check my system if my PC is configured as ACPI, or basic PC configuration. If you can tell me, I'm willing to check it for you. I hope I can help..
cheers

Sorry for the late answer. Switching Z-Buffer on makes the redraw better, if I don't use ASIO. Still not as good as with my old tusl2/win98 setup. However I could live with that, if the Optimaster wouldn't crash scope on project reload in WinXP (never happened on Win98). I think, I'll try to get an old tusl again ..
Thanks for all the help !
Thanks for all the help !
something's hogging resources and the video is suffering. it's not the chipset. driver related? bios? it's NOT normal for xp. 98 was fine and reliable, but things have run much smoother since xp. i've done too many dual monitor machines with cheap evga geforce cards in them with NO problems EVER, including my main 850 based machine. i know that nice matrox card should work flawlessly.
repartion, reformat and reinstall(today's battle-cry. after visiting this forum i'm starting a new daw.). trouble shooting the problem's probably not worth the time. one day's effort should nuke any corrupt system file or improper setting into oblivion.
repartion, reformat and reinstall(today's battle-cry. after visiting this forum i'm starting a new daw.). trouble shooting the problem's probably not worth the time. one day's effort should nuke any corrupt system file or improper setting into oblivion.
Wolf, how much Ram do you have, what speed of HD is XP installed on & does the HD have a cache ??
I can't help directly Wolf, but at one point i remember having terrible problems with Scope Window drawing speeds in XP on an Nforce2 A7N8X deluxe running an Nvidea FX-5200 (128mb) feeding 2 19" CRT's. The system was not installed as Standard PC. In a bid to improve the performance we put in more Ram, which definately helps XP's allround performance, but didn't improve the Scope window drawing performance noticably. It was really bugging us & we were very close to going for a new mobo etc. Eventually i thought sod it, lets get a new 7200 rpm hard disk with 16 meg cache & install XP on that for comparison. So we did just that. Installed XP in Standard PC mode, installed essential drivers & went by the book, you know switching off all the frilly fluffy graphics in XP & generally optimizing the running of the XP OS. After installing Scope, we instantly noticed a very big difference in the drawing/redraw speed of Scope windows accross the screens. It was now very usable indeed. Only problem is
we didn't methodically make the changes one by one, so i can't verify if it was the faster HD with cache or the switch to Standard PC or one of the XP optimizations
If i'm not mistaken, I switched off all networking services in XP & all the other fluff services that we weren't going to need on this 'closed' DAW (no Lan, no Net 
Worked a treat
I can't help directly Wolf, but at one point i remember having terrible problems with Scope Window drawing speeds in XP on an Nforce2 A7N8X deluxe running an Nvidea FX-5200 (128mb) feeding 2 19" CRT's. The system was not installed as Standard PC. In a bid to improve the performance we put in more Ram, which definately helps XP's allround performance, but didn't improve the Scope window drawing performance noticably. It was really bugging us & we were very close to going for a new mobo etc. Eventually i thought sod it, lets get a new 7200 rpm hard disk with 16 meg cache & install XP on that for comparison. So we did just that. Installed XP in Standard PC mode, installed essential drivers & went by the book, you know switching off all the frilly fluffy graphics in XP & generally optimizing the running of the XP OS. After installing Scope, we instantly noticed a very big difference in the drawing/redraw speed of Scope windows accross the screens. It was now very usable indeed. Only problem is



Worked a treat
