• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
tomasz86

[DISCONTINUED] Update Rollup 2 for Windows 2000

108 posts in this topic

I just made a clean CD with your pack and everything went well. Windows2000-KB935839-v5a-x86-ENU.exe

can I use this file on Server 2000?

The reason I ask is because some of BlackWingCat files that work for Win 2000 Pro

doesn't work for the server version.

Edited by PROBLEMCHYLD
0

Share this post


Link to post
Share on other sites

Yes :yes: I think there are no updates at this moment that CAN'T be installed on Win2k Server. You can even install DX Gaming on it ;) Which files are you particularly talking about?

In case of this one I'm sure it works as I'm using it myself on Win2k Advanced Server.

My2GirlsDad,

You may try putting "scripten.exe" in HF instead of HFSVCPACK_SW1.

To summarise:

#1. Use the fixed (v2a) version of IE / OE Mini Rollup 1.1.

#2. Use the kernel v5 together with DX Full Pack (Gaming).

#3. Put "scripten.exe" in HF.

Everything should install fine.

Edited by tomasz86
0

Share this post


Link to post
Share on other sites

I did get a popup usb human interface files are not digitally sign. I had to click yes 4 times to continue with installation.

0

Share this post


Link to post
Share on other sites

Are you sure it was related to the files from BlackWingCat? I would suspect an HBR to be responsible for this.

0

Share this post


Link to post
Share on other sites

Are you sure it was related to the files from BlackWingCat? I would suspect an HBR to be responsible for this.

You might be right, this is what my HF folder looks like I don't use IE6 because I use FDV fileset

MDAC_TYP.EXE

MDAC281-KB2419632-V2-X86-ENU.EXE

MDAC281-KB927779-V2-X86-ENU.EXE

MDAC281-KB954920-V2-X86-ENU.EXE

MDAC281-KB960071-V2-X86-ENU.EXE

MDAC281-KB961451-V2-X86-ENU.EXE

MSXML2.MSI

MSXML2SP6-KB887606-X86-ENU.EXE

MSXML4-KB973685-X86-ENU.EXE

MSXML6-KB973686-X86-ENU.EXE

ROOTSUPD.EXE

WINDOWS2000-KB180410-V2-X86-ENU.EXE

WINDOWS2000-KB2079403-V2-X86-ENU.EXE

WINDOWS2000-KB2115168-X86-ENU.EXE

WINDOWS2000-KB2121546-X86-ENU.EXE

WINDOWS2000-KB2124261-V1A-X86-ENU.EXE

WINDOWS2000-KB2290570-X86-ENU.EXE

WINDOWS2000-KB2347290-X86-ENU.EXE

WINDOWS2000-KB2360937-V2-X86-ENU.EXE

WINDOWS2000-KB2387149-V1A-X86-ENU.EXE

WINDOWS2000-KB2393802-V4-X86-ENU.EXE

WINDOWS2000-KB2412687-X86-ENU.EXE

WINDOWS2000-KB2440591-X86-ENU.EXE

WINDOWS2000-KB2443105-V2-X86-ENU.EXE

WINDOWS2000-KB2476687-V2A-X86-ENU.EXE

WINDOWS2000-KB2479628-V9-X86-ENU.EXE

WINDOWS2000-KB2485663-X86-ENU.EXE

WINDOWS2000-KB2506212-X86-ENU.EXE

WINDOWS2000-KB2507618-V1A-X86-ENU.EXE

WINDOWS2000-KB2511455-V2-X86-ENU.EXE

WINDOWS2000-KB2562937-X86-ENU.EXE

WINDOWS2000-KB2570791-V2-X86-ENU.EXE

WINDOWS2000-KB2641690-X86-ENU.EXE

WINDOWS2000-KB323074-X86-ENU.EXE

WINDOWS2000-KB324446-X86-ENU.EXE

WINDOWS2000-KB328468-X86-ENU.EXE

WINDOWS2000-KB811392-X86-ENU.EXE

WINDOWS2000-KB816972-X86-ENU.EXE

WINDOWS2000-KB817478-X86-ENU.EXE

WINDOWS2000-KB818349-X86-ENU.EXE

WINDOWS2000-KB818383-X86-ENU.EXE

WINDOWS2000-KB818455-X86-ENU.EXE

WINDOWS2000-KB818523-X86-ENU.EXE

WINDOWS2000-KB818801-X86-ENU.EXE

WINDOWS2000-KB819628-X86-ENU.EXE

WINDOWS2000-KB819716-X86-ENU.EXE

WINDOWS2000-KB819745-X86-ENU.EXE

WINDOWS2000-KB819876-X86-ENU.EXE

WINDOWS2000-KB820227-X86-ENU.EXE

WINDOWS2000-KB820525-X86-ENU.EXE

WINDOWS2000-KB820604-X86-ENU.EXE

WINDOWS2000-KB821308-X86-ENU.EXE

WINDOWS2000-KB821394-X86-ENU.EXE

WINDOWS2000-KB822112-X86-ENU.EXE

WINDOWS2000-KB822720-X86-ENU.EXE

WINDOWS2000-KB823442-X86-ENU.EXE

WINDOWS2000-KB823459-X86-ENU.EXE

WINDOWS2000-KB824025-X86-ENU.EXE

WINDOWS2000-KB824428-X86-ENU.EXE

WINDOWS2000-KB824995-V3-X86-ENU.EXE

WINDOWS2000-KB826127-X86-ENU.EXE

WINDOWS2000-KB826978-X86-ENU.EXE

WINDOWS2000-KB827078-X86-ENU.EXE

WINDOWS2000-KB827479-X86-ENU.EXE

WINDOWS2000-KB828047-X86-ENU.EXE

WINDOWS2000-KB828206-X86-ENU.EXE

WINDOWS2000-KB829188-X86-ENU.EXE

WINDOWS2000-KB830051-X86-ENU.EXE

WINDOWS2000-KB830407-V2-X86-ENU.EXE

WINDOWS2000-KB830460-X86-ENU.EXE

WINDOWS2000-KB831375-X86-ENU.EXE

WINDOWS2000-KB831694-X86-ENU.EXE

WINDOWS2000-KB832004-X86-ENU.EXE

WINDOWS2000-KB832940-X86-ENU.EXE

WINDOWS2000-KB834128-X86-ENU.EXE

WINDOWS2000-KB834423-X86-ENU.EXE

WINDOWS2000-KB835365-X86-ENU.EXE

WINDOWS2000-KB835446-X86-ENU.EXE

WINDOWS2000-KB835730-V3-X86-ENU.EXE

WINDOWS2000-KB836111-X86-ENU.EXE

WINDOWS2000-KB836143-X86-ENU.EXE

WINDOWS2000-KB836726-X86-ENU.EXE

WINDOWS2000-KB836740-X86-ENU.EXE

WINDOWS2000-KB837789-X86-ENU.EXE

WINDOWS2000-KB838039-X86-ENU.EXE

WINDOWS2000-KB838141-X86-ENU.EXE

WINDOWS2000-KB838417-X86-ENU.EXE

WINDOWS2000-KB839228-X86-ENU.EXE

WINDOWS2000-KB839264-X86-ENU.EXE

WINDOWS2000-KB840136-X86-ENU.EXE

WINDOWS2000-KB840172-X86-ENU.EXE

WINDOWS2000-KB840629-X86-ENU.EXE

WINDOWS2000-KB840670-X86-ENU.EXE

WINDOWS2000-KB840883-X86-ENU.EXE

WINDOWS2000-KB841031-X86-ENU.EXE

WINDOWS2000-KB841151-X86-ENU.EXE

WINDOWS2000-KB842222-X86-ENU.EXE

WINDOWS2000-KB843125-X86-ENU.EXE

WINDOWS2000-KB843249-X86-ENU.EXE

WINDOWS2000-KB843503-X86-ENU.EXE

WINDOWS2000-KB872771-X86-ENU.EXE

WINDOWS2000-KB872955-X86-ENU.EXE

WINDOWS2000-KB873407-X86-ENU.EXE

WINDOWS2000-KB873437-X86-ENU.EXE

WINDOWS2000-KB883103-X86-ENU.EXE

WINDOWS2000-KB883528-X86-ENU.EXE

WINDOWS2000-KB884536-X86-ENU.EXE

WINDOWS2000-KB884872-X86-ENU.EXE

WINDOWS2000-KB885927-X86-ENU.EXE

WINDOWS2000-KB888111-X86-ENU.EXE

WINDOWS2000-KB889317-X86-ENU.EXE

WINDOWS2000-KB890067-X86-ENU.EXE

WINDOWS2000-KB890188-X86-ENU.EXE

WINDOWS2000-KB890202-X86-ENU.EXE

WINDOWS2000-KB890579-X86-ENU.EXE

WINDOWS2000-KB890756-X86-ENU.EXE

WINDOWS2000-KB891069-X86-ENU.EXE

WINDOWS2000-KB891566-X86-ENU.EXE

WINDOWS2000-KB891861-UR2-V4-X86-ENU.EXE

WINDOWS2000-KB892137-X86-ENU.EXE

WINDOWS2000-KB892294-X86-ENU.EXE

WINDOWS2000-KB892494-X86-ENU.EXE

WINDOWS2000-KB892496-X86-ENU.EXE

WINDOWS2000-KB892924-V2-X86-ENU.EXE

WINDOWS2000-KB892993-X86-ENU.EXE

WINDOWS2000-KB894869-X86-ENU.EXE

WINDOWS2000-KB895266-X86-ENU.EXE

WINDOWS2000-KB896260-V2-X86-ENU.EXE

WINDOWS2000-KB896674-V2-X86-ENU.EXE

WINDOWS2000-KB896712-X86-ENU.EXE

WINDOWS2000-KB897574-V3-X86-ENU.EXE

WINDOWS2000-KB897711-X86-ENU.EXE

WINDOWS2000-KB898465-X86-ENU.EXE

WINDOWS2000-KB898710-X86-ENU.EXE

WINDOWS2000-KB899904-X86-ENU.EXE

WINDOWS2000-KB900623-X86-ENU.EXE

WINDOWS2000-KB901377-X86-ENU.EXE

WINDOWS2000-KB904375-X86-ENU.EXE

WINDOWS2000-KB904711-V2-X86-ENU.EXE

WINDOWS2000-KB905488-X86-ENU.EXE

WINDOWS2000-KB906569-X86-ENU.EXE

WINDOWS2000-KB907980-X86-ENU.EXE

WINDOWS2000-KB909916-X86-ENU.EXE

WINDOWS2000-KB911018-X86-ENU.EXE

WINDOWS2000-KB911589-X86-ENU.EXE

WINDOWS2000-KB915365-V2-X86-ENU.EXE

WINDOWS2000-KB917423-X86-ENU.EXE

WINDOWS2000-KB919862-X86-ENU.EXE

WINDOWS2000-KB922667-X86-ENU.EXE

WINDOWS2000-KB922823-X86-ENU.EXE

WINDOWS2000-KB927489-V2-X86-ENU.EXE

WINDOWS2000-KB932590-X86-ENU.EXE

WINDOWS2000-KB935839-V5A-X86-ENU.EXE

WINDOWS2000-KB950305-V2-X86-ENU.EXE

WINDOWS2000-KB954193-X86-ENU.EXE

WINDOWS2000-KB968006-X86-ENU.EXE

WINDOWS2000-KB977377-X86-ENU.EXE

WINDOWS2000-KB978706-V2-X86-ENU.EXE

WINDOWS2000-KB979687-V2-X86-ENU.EXE

WINDOWS2000-KB980232-X86-ENU.EXE

WINDOWS2000-KB981322-X86-ENU.EXE

WINDOWS2000-KB982132-X86-ENU.EXE

WINDOWS2000-KB982665-V2-X86-ENU.EXE

WINDOWS2000-SCRIPT58-X86-ENU.EXE

WINDOWS2000-WINDOWSMEDIA-KB975558-X86-ENU.EXE

WINDOWS-KB890830-V4.1.EXE

WINDOWS-KB909520-V1.000-X86-ENU.EXE

Edited by PROBLEMCHYLD
0

Share this post


Link to post
Share on other sites

tomasz86,

about a week ago, I ran 2K setup from CD to machine installs and setup had problems installing shlwapi.dll (as did My2GirlsDad) as well as two others

odbc32.dll

mswrd6.wpc

just in case it might help while you are reviewing

they occurred at different times in the setup (see pics)

unfortunately I don't have the log files anymore

post-79406-0-63615300-1310922979_thumb.j

post-79406-0-06078500-1310923048_thumb.j

0

Share this post


Link to post
Share on other sites

#2. Use the kernel v5 together with DX Full Pack (Gaming).

This is the fix for

SCRIPTEN.EXE

WINDOWS2000-KB975542-X86-ENU.EXE

WINDOWS2000-KB981349-X86-ENU.EXE

everything slipstream fine no errors.

It was fdv fileset that caused the usb interface popup, I know this because I slipstream a CD without fdv fileset and there was no errors.

Thank you! You are 1 awesome person.

0

Share this post


Link to post
Share on other sites

Molecule,

odbc32.dll is caused by the broked header of KB2419632. I posted about it long time ago here

You should try using the Global version (v2) which has this problem fixed.

Windows2000-KB2419632-v2-x86-Global.exe

PROBLEMCHYLD,

are there any problems with the above updates (scripten.exe, KB975542, KB981349) when not using the kernel v5?

0

Share this post


Link to post
Share on other sites

My2GirlsDad,

You may try putting "scripten.exe" in HF instead of HFSVCPACK_SW1.

To summarise:

#1. Use the fixed (v2a) version of IE / OE Mini Rollup 1.1.

#2. Use the kernel v5 together with DX Full Pack (Gaming).

#3. Put "scripten.exe" in HF.

Everything should install fine.

Thank you very much, tomasz86, everything installed just like it should with no problems.

Appreciate your quick fixes.

Waiting patiently for your update to Update Rollup 2 for Windows 2000 with WMP9 and MDAC 2.8. Take your time I can wait.

My2GirlsDad

0

Share this post


Link to post
Share on other sites

PROBLEMCHYLD,

are there any problems with the above updates (scripten.exe, KB975542, KB981349) when not using the kernel v5?

Yes I get the same error My2GirlsDad was talking about, doesn't matter what folder you use. I always had to install them manually.

Your tip help a lot. thanks

Edited by PROBLEMCHYLD
0

Share this post


Link to post
Share on other sites

My2GirlsDad,

It's good to know that everything works now :) As for MDAC 2.81, it will be included in UR2.1. WMP9 - I'm still now sure whether to include it in UR2.1 or just make a separate package.

PROBLEMCHYLD,

Interesting... I got no errors when putting scripten.exe in HF (and I didn't slipstream anything else apart from it to be sure that it was scripten.exe to cause that error). Anyway, I always recommend using BlackWingCat's kernel (v5) as it extends Win2k kernel by adding functions from the XP one. Many programs which normally don't work under 2K can be run with no problems when this kernel is installed.

Edited by tomasz86
0

Share this post


Link to post
Share on other sites

My2GirlsDad,

It's good to know that everything works now :) As for MDAC 2.81, it will be included in UR2.1. WMP9 - I'm still now sure whether to include it in UR2.1 or just make a separate package.

PROBLEMCHYLD,

Interesting... I got no errors when putting scripten.exe in HF (and I didn't slipstream anything else apart from it to be sure that it was scripten.exe to cause that error). Anyway, I always recommend using BlackWingCat's kernel (v5) as it extends Win2k kernel by adding functions from the XP one. Many programs which normally don't work under 2K can be run with no problems when this kernel is installed.

The errors only occur when I don't use BlackWingCat's kernel, sorry you misunderstood me. Everything works great.

0

Share this post


Link to post
Share on other sites

That's what I'm talking about :lol: I don't get any errors even if NOT using the BWC kernel.

Edited by tomasz86
0

Share this post


Link to post
Share on other sites

WINDOWS2000-KB838969-X86-ENU.EXE

I quckly checked your list of updates and I can say for sure that this one is obsolete.

0

Share this post


Link to post
Share on other sites

WINDOWS2000-KB838969-X86-ENU.EXE

I quckly checked your list of updates and I can say for sure that this one is obsolete.

That one is replaced by 961063 - Dns.exe 5.0.2195.7260.

0

Share this post


Link to post
Share on other sites

That's what I'm talking about :lol: I don't get any errors even if NOT using the BWC kernel.

Was you using scripten.exe 5.7? This is the version I'm talking about. All other version work with or without BWC kernel..

0

Share this post


Link to post
Share on other sites

Yes :yes:

I did a test especially to check if Script 5.7 (scripten.exe) can be slipstreamed from HF. No problems occured.

Edited by tomasz86
0

Share this post


Link to post
Share on other sites

tomasz86,

I've come across another potential problem with your Update Rollup 2. Below find my results at Microsoft Update after my latest slipstream using HFSLIP.

While I understand that KB908531 and KB982381 are due to unofficial update KB2416400, I was surprised that KB956844 showed up since it part of the Rollup.

If I include the KB956844 in the \HF folder it updates TRIEDIT.dll to version 6.1.0.9235. If I leave it out and rely on the Rollup, triedit.dll remains at version 6.1.0.9211.

Is this something you may have overlooked? Everything else seems to working fine.

Thanks for looking into this.

My2GirlsDad

0

Share this post


Link to post
Share on other sites

My2GirlsDad,

I know about this triedit.dll problems. It is caused by HFSLIP. Please make sure that before running HFSLIP you remove the following files:

HFCABS\_IE6_HFSLIP.CAB
HFCABS\_IE6b_HFSLIP.CAB
HFCABS\_OE6_HFSLIP.CAB

They are temporary files created by HFSLIP in order to slipstream IE/OE 6. The problem is that they mess the dates of these files and the older version of triedit.dll gets slipstreamed because of that. After running HFSLIP you should check file version of triedit.dl_ (unpack it first) from i386\. I had the same problem with triedit.dll but after removing these files the proper version gets slipstreamed. Be aware that they are created each time you run HFSLIP (if IE6 cabs are present) so you ought to delete them also each time before running HFSLIP.

You may also try using the beta of UR2-v3 which I optimised especially for compatibility with WU.

Windows2000-KB891861-UR2-v3-BETA-x86-ENU.exe (pass: msfn)

UR2-v3 has also the following improvements:

  • - KB908531 is marked as installed (although the verclsid.exe file itself is just a dummy file, not used by the system)
    - ocsasnfix.exe is included (you had this one in your HFSLIP log, it's not necessary anymore :))

There are also more fixes and new updates but I'm going to explain everything in details when the final version is ready. You can check eula (update\eula.txt) for a full list of updates included in UR2-v3-BETA. NO updates are available through WU after the installation of UR2-v3 :whistle:

Edited by tomasz86
0

Share this post


Link to post
Share on other sites

My2GirlsDad,

I know about this triedit.dll problems. It is caused by HFSLIP. Please make sure that before running HFSLIP you remove the following files:

HFCABS\_IE6_HFSLIP.CAB
HFCABS\_IE6b_HFSLIP.CAB
HFCABS\_OE6_HFSLIP.CAB

They are temporary files created by HFSLIP in order to slipstream IE/OE 6. The problem is that they mess the dates of these files and the older version of triedit.dll gets slipstreamed because of that. After running HFSLIP you should check file version of triedit.dl_ (unpack it first) from i386\. I had the same problem with triedit.dll but after removing these files the proper version gets slipstreamed. Be aware that they are created each time you run HFSLIP (if IE6 cabs are present) so you ought to delete them also each time before running HFSLIP.

You may also try using the beta of UR2-v3 which I optimised especially for compatibility with WU.

Windows2000-KB891861-UR2-v3-BETA-x86-ENU.exe (pass: msfn)

UR2-v3 has also the following improvements:

  • - KB908531 is marked as installed (although the verclsid.exe file itself is just a dummy file, not used by the system)
    - ocsasnfix.exe is included (you had this one in your HFSLIP log, it's not necessary anymore :))

There are also more fixes and new updates but I'm going to explain everything in details when the final version is ready. You can check eula (update\eula.txt) for a full list of updates included in UR2-v3-BETA. NO updates are available through WU after the installation of UR2-v3 :whistle:

tomasz86,

After trying both of your great tips, removing the HFSLIP cab files and using your beta version, I'm still getting the 6.1.0.9211 version of triedit.dll instead of 6.1.0.9235. As I said before if I put KB956844 in HF the file is updated correctly. Is there something different between KB956844 and your rollup?

Thanks for your input on this. It is very confusing to me.

My2girlsDad

0

Share this post


Link to post
Share on other sites

Could you try slipstreaming only IE6 cabs and UR2-v3?

I've just done a test:

Files in your HF folder:

Windows2000-KB891861-UR2-v3-BETA-x86-ENU.exe

Files in your HFCABS folder:

_IE6_HFSLIP.CAB

_IE6b_HFSLIP.CAB

_OE6_HFSLIP.CAB

BRANDING.CAB

IEW2K_1.CAB

IEW2K_2.CAB

IEW2K_3.CAB

IEW2K_4.CAB

MAILNEWS.CAB

OEEXCEP.CAB

WAB.CAB

and the result is triedit.dll 6.1.0.9235.

Edited by tomasz86
0

Share this post


Link to post
Share on other sites

Could you try slipstreaming only IE6 cabs and UR2-v3?

I've just done a test:

Files in your HF folder:

Windows2000-KB891861-UR2-v3-BETA-x86-ENU.exe

Files in your HFCABS folder:

_IE6_HFSLIP.CAB

_IE6b_HFSLIP.CAB

_OE6_HFSLIP.CAB

BRANDING.CAB

IEW2K_1.CAB

IEW2K_2.CAB

IEW2K_3.CAB

IEW2K_4.CAB

MAILNEWS.CAB

OEEXCEP.CAB

WAB.CAB

and the result is triedit.dll 6.1.0.9235.

tomasz86,

I believe I've found the reason that triedit.dll was not updated. It seems that HFSLIP was set up to do the original update rollup 1 first (I'm not sure why), then the IE cabs files, then the remaining hotfixes. This causes the triedit.dll from your Rollup, because it has the same KB number, to be overwritten by the IE cabs.

When I changed the name of your Rollup from Windows2000-KB891861-UR2-v3-BETA-x86-ENU.exe to Windows2000-KB891UR2861-v3-BETA-x86-ENU.exe the file was updated and KB956844 disappeared from Microsoft Updates.

With that problem fixed I still have one issue with the Rollup. Microsoft Update still asks for KB982381 Cumulative Security Update for IE6 SP1. KB908531 no longer shows up.

Thanks for your continued help.

Regards,

My2GirlsDad

0

Share this post


Link to post
Share on other sites

My2GirlsDad,

Update Rollup 1(or 2) being slipstreamed before everything else is a normal HFSLIP behaviour. Still it shouldn't have any influence on triedit.dll. I did a few more tests and the version slipstreamed was always 6.1.0.9235.

Are you sure you removed the SOURCESS folder before running HFSLIP?

The reason why UR is slipstreamed first is that in contains several Server related files and they are deleted by HFSLIP if your 2K version is Professional. They won't be deleted if you change the KB number (it has to be *KB891861*).

I uploaded v3 of Update Rollup 2.

Changes:

  • - added two Script updates (KB975542, KB981349); bristols says they're for Script 5.6 only but in reality they are for both Script 5.1 & 5.6 (but not for 5.7!)
    - added two Media Services updates (KB952068, KB980858); (installed only when Media Services are present)
    - added ocsasnfix.exe (fix related to KB974571)
    - improved compatiblity with Windows Update
    - version of UR2 is now shown in System Properties (see screen shot below)

eDvtp.png

Unfortunately I also have bad news. This is the last version of UR2 and I am not going to update it anymore unless bugs are found.

Plans for UR2.1 are cancelled.

Edited by tomasz86
0

Share this post


Link to post
Share on other sites

are you leaving the scene?

0

Share this post


Link to post
Share on other sites

are you leaving the scene?

No no, don't worry :lol:

The structure of an update rollup has too many limitations and the need to keep compatibility with HFSLIP also limits greatly my room to manoeuvre. For this reason I decided to focus on a bigger project which will not depend neither on HFSLIP nor on any other 3rd party application in order to be slipstreamed. It's going to take a lot of time (months) but the result should be much more satisfying than now with UR2.

Update Rollups are quite easy to make but I need more functions which they lack. To give an example - it's impossible to include Server-only updates in UR2 and keep full HFSLIP compatibility at the same time. The only way to do it would be to modify the HFSLIP itself which I want to avoid as I'm not the author of it.

UR2 in this form is kind of completed as it has all of the vital updates included. The only ones left are the buggy updates, Server-only updates and updates for non-default components (MDAC 2.81, WMP9, etc.).

Anyway, this is my plan for the future. I won't unveil more information as it's still too early to say for sure that everything I want to do is possible. I'll let you know in due course ;)

Edited by tomasz86
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.