Announcement

Collapse
No announcement yet.

Matrox have done it again :(

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Miya

    My ire has not waned a) because of all the hoo-hah necessary to get it working and b) because I believe the real cause was that WIN98 was on the C: partition in FAT32 and W2k was on the E: partition in NTFS. I noticed that part of the W2k driver installation was on the C: drive. Before the original installation I'd deleted everything findable in the W2k registry pertainable to Matrox. Before I reformatted everything, there were 2 or 3 registry references under Matrox to C:\windows\... and not to E:\winnt\... (this was what inspired me to go the whole hog and reformat). In other words, it is my belief that the drivers installation looked for the first Windows installation it could find to put in some of the files and not necessarily the active one (maybe because the same files were already there under the W98 installation). Whatever, it was a balls-up that has cost me at least two days altogether.

    Zeb7

    In both cases, the DirectX was identical. (8.0 + DV update).

    I added those items that you suggested that were missing from ulead32.ini. I must admit that I'd forgotten about this file as it's years since I had to adjust it: thanks for reminding me. Unfortunately, your suggestions have made no difference to the scrubbing problem, but it has given me a useful reminder where to start looking. Unfortunately, I hadn't thought about recording what was on mine before rehashing the computer I'll do some research along these lines. Unfortunately, Ulead don't give explanations of their arcane settings, that I know of.

    Mikie

    Thanks for your suggestions. It has taken me till now, to take the jump to W2k/SP2. I've no intention of going to XP for a long time yet. I'm not intrepid enough to rush into OS changes before everything has been debugged. I even disinstalled W ME that came with a computer a year or so ago and upgraded it to W98SE. If I had my way, I'd still be on MS-DOS 6.2 Actually, as an old-timer in computers, I hate ALL GUIs which serve only to bloat and to slow down everything. Believe it or not, I often use a DOS-like shell in Windows on my office computer. Amazing how quick it is, compared with using a mouse. Anyway, if I can solve this scrubbing lark, I'll probably stick with W2k for video work, if only for the convenience for the file sizes. I'm stuck with 98SE for the office computer, as I don't have drivers later than W98 for a couple of oldish pro peripherals.

    Thanks for everything, chaps!
    Brian (the devil incarnate)

    Comment


    • #17
      I have the problem solved, now (at least, I think so). It was a question of DirectX. Apparently, there is an incompatibility between 8.0, with or without the DV update, and MSP under W2k under some unspecified conditions. V. 8.1 cures the problem. I wonder why Ulead don't put this in their FAQs???? I received a helpful reply from Ulead tech support.
      Brian (the devil incarnate)

      Comment

      Working...
      X