Omega Owners Forum
Chat Area => General Discussion Area => Topic started by: Martin_1962 on 28 October 2006, 23:31:17
-
Started getting serious flickering - nothing fixed it so I bought a new graphics card - little around now for AGP so I got a Leadtek A7600 - well it had lots of memory and lots of big numbers.
Took 3 hours to get drivers to work because that rubbish gates company sets PCI permissions in the registry to none
However all works well now and seams good for games and playing videos
-
I had serious flickering too recently.
Loaded new drivers. Still the same. Fiddled with settings. No good.
Turned out to be me poor ol' eyes. Large mug of Horlicks and a good sleep soon sorted that problem out.
-
Started getting serious flickering - nothing fixed it so I bought a new graphics card - little around now for AGP so I got a Leadtek A7600 - well it had lots of memory and lots of big numbers.
Took 3 hours to get drivers to work because that rubbish gates company sets PCI permissions in the registry to none
However all works well now and seams good for games and playing videos
Erm, if it is an AGP card, why are you worried about the PCI permissions (I may be missing something as it's been a while)?
I've never had to change them when fitting a new card..
Still it is all good now and that is the important thing. :)
-
Started getting serious flickering - nothing fixed it so I bought a new graphics card - little around now for AGP so I got a Leadtek A7600 - well it had lots of memory and lots of big numbers.
Took 3 hours to get drivers to work because that rubbish gates company sets PCI permissions in the registry to none
However all works well now and seams good for games and playing videos
Erm, if it is an AGP card, why are you worried about the PCI permissions (I may be missing something as it's been a while)?
I've never had to change them when fitting a new card..
Still it is all good now and that is the important thing. :)
Last time I changed my AGP card in my desktop (for a DVI one) I just had to install driver and away it went.....some Dell's are fussy which PCI slot you use, but i thought that only applied to network cards :-/
-
What is the video chipset. AFAIK, for Nvidia and ATI/AMD based cards, Leadtek use the standard manufacturer supplied drivers...
-
Started getting serious flickering - nothing fixed it so I bought a new graphics card - little around now for AGP so I got a Leadtek A7600 - well it had lots of memory and lots of big numbers.
Took 3 hours to get drivers to work because that rubbish gates company sets PCI permissions in the registry to none
However all works well now and seams good for games and playing videos
Erm, if it is an AGP card, why are you worried about the PCI permissions (I may be missing something as it's been a while)?
I've never had to change them when fitting a new card..
Still it is all good now and that is the important thing. :)
Well it wouldn't accept some data or other - search and according to the monopoly it was registry permissions
-
What is the video chipset. AFAIK, for Nvidia and ATI/AMD based cards, Leadtek use the standard manufacturer supplied drivers...
I'll have to have a look
-
Oh and some Intel server motherboards (carnt remember which one now) are fussy which pci slot you plug a raid controller into......i spent 2 days trying to get a raid controller to work....and about 4 hours onto tech support in germany for intel......turned out to be wrong pci slot i plugged it into.....moved it one slot and it worked !! ::)
-
Is it PCI or PCI-Express?
Secondly, I have never heard of this PCI permissions thing. Leadtek usually make nVidia cards which don't require any special tweaking to my knowledge. They also use standard manufacturer drivers, available on nVidia site.
I know you got it fixed now, but I'm still curious about the above permissions thing. I've built a lot of PC's, new and old and not had a problem like it yet.
-
Is it PCI or PCI-Express?
Secondly, I have never heard of this PCI permissions thing. Leadtek usually make nVidia cards which don't require any special tweaking to my knowledge. They also use standard manufacturer drivers, available on nVidia site.
I know you got it fixed now, but I'm still curious about the above permissions thing. I've built a lot of PC's, new and old and not had a problem like it yet.
Leadtek also do ATI based, and some nasty ones based on cheap, old chips similar to s3, SiS etc...
-
THis one is nvidia and is good
-
THis one is nvidia and is good
Thats odd, as Leadtek usually follow Nvidias reference design, and use standard drivers. Not heard of this problem before though. Which Nvidia chip is it using? Which Detonator ver are you running?
-
I'll check later
-
Is it PCI or PCI-Express?
Secondly, I have never heard of this PCI permissions thing. Leadtek usually make nVidia cards which don't require any special tweaking to my knowledge. They also use standard manufacturer drivers, available on nVidia site.
I know you got it fixed now, but I'm still curious about the above permissions thing. I've built a lot of PC's, new and old and not had a problem like it yet.
Leadtek also do ATI based, and some nasty ones based on cheap, old chips similar to s3, SiS etc...
True. The majority are nVidia, hence why i said usually :P. s3 and SiS are nasty. First hand experience here :D
-
Is it PCI or PCI-Express?
Secondly, I have never heard of this PCI permissions thing. Leadtek usually make nVidia cards which don't require any special tweaking to my knowledge. They also use standard manufacturer drivers, available on nVidia site.
I know you got it fixed now, but I'm still curious about the above permissions thing. I've built a lot of PC's, new and old and not had a problem like it yet.
Leadtek also do ATI based, and some nasty ones based on cheap, old chips similar to s3, SiS etc...
True. The majority are nVidia, hence why i said usually :P. s3 and SiS are nasty. First hand experience here :D
Not just nasty but evil too they do not allow VGA DOS graphic applications to run, my work PC has a Inno3D GeForce4 MX 440/440SE according to device manager and that does VGA graphics but not as well as my old W98 PC which allowed me to run them in windows (S3 Trio 32/64PCI)
Gamer cards like my home PC do run DOS VGA quite well!
-
I currently use an ATI x800 - rather impressive gaming card. Lasted me 2 good years now.
-
GeForce4 MX 440/440SE
Slow, awful, horrible card, even when it was released around 4 or 5 yrs ago....
-
GeForce4 MX 440/440SE
Slow, awful, horrible card, even when it was released around 4 or 5 yrs ago....
But cheap... veeery cheap. And a reliable backup for fried Geforce 4 TI models! (I blew two 4600's up!)
-
GeForce4 MX 440/440SE
Slow, awful, horrible card, even when it was released around 4 or 5 yrs ago....
Yes but my work PC is not a games machine, my three year old home PC will eat any at work for breakfast - even though it is a P4 2.4.
We have found that virtually any NVidia chipped card will do VESA 2 but SIS are horrible.
Currently trying to work out why our DOS software runs 20x quicker if I hold the CTRL down - any change I do buggers something else up. It is to do with data access and the dos app taking as much as it can get depriving the IP thunking layer of its priority - I think I'll take ADSDOSIP up to a higher priority and try that.
Some customers are not interested in moving to our WIndows app either
-
As I've said several times, shouldn't really be using DOS stuff (or Win9x stuff) now....
-
As I've said several times, shouldn't really be using DOS stuff (or Win9x stuff) now....
I suppose mainframes shouldn't be used either?
There is still a large amount of DOS applications out there working day in day out.
-
As I've said several times, shouldn't really be using DOS stuff (or Win9x stuff) now....
I suppose mainframes shouldn't be used either?
There is still a large amount of DOS applications out there working day in day out.
Mainframes still have a big role to play. Fortunately, they are normally supported by vendor nowadays, who ensure the OS images are kept up to date.
There are a number of DOS apps, fortunately reducing all the time. The fact that it is a DOS app implies it hasn't been updated for 5 years. That is not good, esp if networked.
-
As I've said several times, shouldn't really be using DOS stuff (or Win9x stuff) now....
I suppose mainframes shouldn't be used either?
There is still a large amount of DOS applications out there working day in day out.
Mainframes still have a big role to play. Fortunately, they are normally supported by vendor nowadays, who ensure the OS images are kept up to date.
There are a number of DOS apps, fortunately reducing all the time. The fact that it is a DOS app implies it hasn't been updated for 5 years. That is not good, esp if networked.
Excuse me I updated our barcode generation today and my boss added a new Spacer bender
-
Excuse me I updated our barcode generation today and my boss added a new Spacer bender
And what tools did you use to do the update, and when where those last updated?
There are (very) few exceptions, but I think you see my point.... ;)
-
Excuse me I updated our barcode generation today and my boss added a new Spacer bender
And what tools did you use to do the update, and when where those last updated?
There are (very) few exceptions, but I think you see my point.... ;)
Mix of Clipper 5.3b and MSC8
-
Excuse me I updated our barcode generation today and my boss added a new Spacer bender
And what tools did you use to do the update, and when where those last updated?
There are (very) few exceptions, but I think you see my point.... ;)
Mix of Clipper 5.3b and MSC8
Clipper 5.3 is circa mid 1990s, and I believe no longer supported by vendor...
-
Is MSC8 MS C++? If so, didn't know it could do DOS apps. I know it can do Win32 console apps.
-
Is MSC8 MS C++? If so, didn't know it could do DOS apps. I know it can do Win32 console apps.
Quick history
Nantucket split off from Ashon Tate as they wanted to do a compiler rather than interpreter, their 5th version of Clipper was 5.01 got bought up by Computer Associates at some time
Summer 87, 5.01, 5.2 all written in MSC5, Clipper 5.3 written in MSC8.
To use extend API for C code you are best using the same compiler ie MSC5 (which is buggier than 8) or MSC8.
MSC8 is part of VC1 and VC1.5, we use VC4 with Alaska Xbase++ and VC6 with Visual Objects.
All three are part of the XBASE family, other members were dBaseII/Vulcan, dBaseIII, dBaseIV, FoxBase, FoxPro, Visual FoxPro. All the dBase were pure interpreter, all Foxes souped up interpreters, and all Clippers PCode compilers (one of the best PCODE compilers ever according to a guru I know (John Skelton)), Nantuckets full compiler project was called Aspen and caused their purchase by CA, the Aspen project was merged with their windows project and became Visual Objects, after a few years it actually became usable.
Parallel tools were Blinker (their first project was ALINK) which became the most popular linker for Clipper, now on version 7, a reindexing engine written as an NLM became a client server engine called Advantage Xbase Server - originally only worked with Clipper, until a windows front end was brought in, now very popular in Delphi, Alaska, VO and of course Clipper circles - available on Netware, NT or Linux.
Clipper was a landmark product as the finest DOS database development system.
We have 4 different languages hitting our databases Via ADS (Xbase became Database)
BTW Visual Basic is horrid!
-
Quick history:
DOS = older than me. Enough said for reasons why it shouldn't be in use any more! HCI has changed so much that command line input is cumbersome, time consuming and incredibly complicated considering what can be done these days.
For the record, I used to love DOS and general command input. Just can't use it these days though.
And btw... Visual Basic is superb! I've drawn/written loads of home made apps and programs to do the things I want! I couldnt do without it. Quick, easy and no frills :D Just like basic in DOS, but with a GUI.
-
Certain tasks are so much easier on the command line
Directory creating.
mapping drives
seeing actual file size quickly
Running anything with command line parameters
-
Is MSC8 MS C++? If so, didn't know it could do DOS apps. I know it can do Win32 console apps.
Quick history
Nantucket split off from Ashon Tate as they wanted to do a compiler rather than interpreter, their 5th version of Clipper was 5.01 got bought up by Computer Associates at some time
Summer 87, 5.01, 5.2 all written in MSC5, Clipper 5.3 written in MSC8.
To use extend API for C code you are best using the same compiler ie MSC5 (which is buggier than 8) or MSC8.
MSC8 is part of VC1 and VC1.5, we use VC4 with Alaska Xbase++ and VC6 with Visual Objects.
All three are part of the XBASE family, other members were dBaseII/Vulcan, dBaseIII, dBaseIV, FoxBase, FoxPro, Visual FoxPro. All the dBase were pure interpreter, all Foxes souped up interpreters, and all Clippers PCode compilers (one of the best PCODE compilers ever according to a guru I know (John Skelton)), Nantuckets full compiler project was called Aspen and caused their purchase by CA, the Aspen project was merged with their windows project and became Visual Objects, after a few years it actually became usable.
Parallel tools were Blinker (their first project was ALINK) which became the most popular linker for Clipper, now on version 7, a reindexing engine written as an NLM became a client server engine called Advantage Xbase Server - originally only worked with Clipper, until a windows front end was brought in, now very popular in Delphi, Alaska, VO and of course Clipper circles - available on Netware, NT or Linux.
Clipper was a landmark product as the finest DOS database development system.
We have 4 different languages hitting our databases Via ADS (Xbase became Database)
BTW Visual Basic is horrid!
know history of clipper. I had assumed you were talking Visual C 8, not the original that was left unsupportted before my grandad was born.
Really should be using more up to date stuff now, as these tools are unsupportted, hence go unfixed.
Classic VB has its place, but again is on verge of being unsupported, hence should be dropped. VB.NET is a good language.