Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×


  • Content Count

  • Joined

  • Last visited

  • Donations


Community Reputation

0 Neutral

About Brimborium

Profile Information

  • OS
    none specified
  1. For some reason, Google's SafeBrowsing service mistakes vorck.com and the update lists as "suspicious" - http://safebrowsing.clients.google.com/saf...fixes_2000.html They suggest this action: http://www.stopbadware.org/home/reviewinfo...fixes_2000.html
  2. Thanks for the new beta version to fix the DX9 issue, tommyp. KB961373 integrates without problems now, and the same goes for MSXML 4.0 SP3 (thanks James_A for the hint) if you replace msxml4-KB954430 with msxml.msi in the HF folder. However, there is a small cosmetic glitch: HFSLIP.log and control panel still show 1.7.9_beta_h instead of i.
  3. There seems to be a problem with Windows 2000 and the new DX9 hotfix (KB961373): hfslip 1.7.9_beta_h doesn't seem to recognize it as DX-specific while slipstreaming, i.e. unlike KB951698-v2 it will be extracted like a normal hotfix, and is also offered on Microsoft Update afterwards. The rest of this week's patchday seems to work fine though. My config: Win2k Pro German IE6 SP1 + WMP 6.4 DX9c original release MDAC 2.81 SP1 MSXML 4.0 SP2 + 6.0 SP2
  4. Oops, I somehow forgot to check this link, sorry. Unfortunately it seems AVG Free users can't use the technical support form either ("The license number you have entered belongs to AVG Free. No premium support is available for AVG Free."), but I found a E-Mail address (virus@avg.com) in the forum which claims to be working for reporting false detections. I'll write them a letter later today, but still it would be nice if someone with a paid licence could lend us a hand.
  5. Hello, I've also encountered a warning of my AVG Free 8.5 after downloading your tool, but as said this should be a false positive. However, the affected file was send to AVG's Research Lab (via virus fault -> send to analysis) and here are the results: Maybe you should try to contact AVG's technical support manually to solve this problem; my other machine running AntiVir Personal along with other scanners don't report anything. Apart from that, thank you for this .NET setup maker - much more comfortable then to use six MSI packages at T-13.
  • Create New...