Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Developer Toolkits / March 2006

Tip: Looking for answers? Try searching our database.

List of Access XP Runtime modifications

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
George Nicholson - 13 Mar 2006 21:54 GMT
I know about MSKB article 837150 "You may get error message when you install
an Access 2002 runtime deployment package on a computer that is running
Windows XP SP2 or Windows Server 2003"

The workaround for this is to remove a line from Ospfilelist.txt in the
Packaging wizard, then recreate the package.
(Note: reading the article leads one to think that removing the line causes
no problems even if you aren't getting the error, but they don't come right
out and say it's an unnecessary line.)

My question is this: does anyone have a list of known/standard workarounds
that require similar tweaks to Packaging wizard or Runtime files? (I'm
thinking "this can't be the only one like this...", but maybe it is.)

I'm in a situation where I need to prepare a package that one of the
partners can install at a clients. Needless to say, everyone would like this
to work like a charm the first time. I know that nothing can ever be
guaranteed to be 100% error free, but I'd like to prepare a package that
conventional wisdom (that's you guys & gals) says is as close to that as
possible.

TIA,
Signature

George Nicholson

Remove 'Junk' from return address.

Tony Toews - 14 Mar 2006 22:05 GMT
>My question is this: does anyone have a list of known/standard workarounds
>that require similar tweaks to Packaging wizard or Runtime files? (I'm
>thinking "this can't be the only one like this...", but maybe it is.)

I don't recall any other such but I sure could be wrong.  Searching
the KB using the right keywords, such as packaging wizard or
deployment or whatever might find some more but who can say.

>I'm in a situation where I need to prepare a package that one of the
>partners can install at a clients. Needless to say, everyone would like this
>to work like a charm the first time. I know that nothing can ever be
>guaranteed to be 100% error free, but I'd like to prepare a package that
>conventional wisdom (that's you guys & gals) says is as close to that as
>possible.

The biggest problem is going to be if they already have Access
installed.   Or if they install another Access runtime after yours is
installed.

Microsoft Access (Office) Developer Edition FAQ
http://www.granite.ab.ca/access/developereditionfaq.htm

Tony
Signature

Tony Toews, Microsoft Access MVP
  Please respond only in the newsgroups so that others can
read the entire thread of messages.
  Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

Chris Mills - 16 Mar 2006 09:25 GMT
Tony,
your re-vamped web-site in regards to direct hacking software advertising
remains completely inadequate, IMHO.

Please sort yourself and your website out. It brings shame on all so-called
Microsoft MVP awardees.

The subject of hacking support is by no means at rest.

Chris

(so far as I can tell at a glance, the self-described "junkie" Jeff Conrad has
at least had the decency, probably under instruction, to review his
contribution to hacking. His withering irresponsibility will forever remain
exemplary)

"Tony Toews" <ttoews@telusplanet.net> wrote in message
>blah-blah
Alex Dybenko - 16 Mar 2006 11:07 GMT
Chris,
just wondering - what is "direct hacking software" you are talking about?

Signature

Alex Dybenko (MVP)
http://alexdyb.blogspot.com
http://www.PointLtd.com

> Tony,
> your re-vamped web-site in regards to direct hacking software advertising
[quoted text clipped - 17 lines]
> "Tony Toews" <ttoews@telusplanet.net> wrote in message
>>blah-blah
Chris Mills - 16 Mar 2006 19:39 GMT
Direct:
1) extending or moving in a straight line or by the shortest route
2) straighforward; going straight to the point.

Hack:
1) Cut or chop roughly; mangle
2) a horse for ordinary riding

Software:
opp: hardware

HTH
Chris :-)

What we have here, is a purportedly valued MVP (Tony Toews) providing direct
advertising of some Rumanian Software Hacker. That's just a fact. I am
therefore asking for Tony Toews MVP status to be reviewed. It is no longer
possible that he's "unaware". He is "complicit in hacking".

> Chris,
> just wondering - what is "direct hacking software" you are talking about?
Alex Dybenko - 17 Mar 2006 06:58 GMT
Well, I know what the words mean, I asked about link on his web site where
he advertising "direct hacking software"
I did not find one
and knowing Tony - I think he always put good links on his site <g>

Signature

Alex Dybenko (MVP)
http://alexdyb.blogspot.com
http://www.PointLtd.com

> Direct:
> 1) extending or moving in a straight line or by the shortest route
[quoted text clipped - 18 lines]
>> Chris,
>> just wondering - what is "direct hacking software" you are talking about?
Chris Mills - 18 Mar 2006 23:54 GMT
Well, it's there in plain rumanian.

> I did not find one
Alex Dybenko - 19 Mar 2006 20:23 GMT
ok, go ahead, no problem, i can understand Romanian

> Well, it's there in plain rumanian.
>
>> I did not find one
Tony Toews - 16 Mar 2006 20:14 GMT
>your re-vamped web-site in regards to direct hacking software advertising
>remains completely inadequate, IMHO.

I didn't realize I had revamped anything.

>Please sort yourself and your website out. It brings shame on all so-called
>Microsoft MVP awardees.

Security by obscurity doesn't work.

>The subject of hacking support is by no means at rest.

Then we disagree.

Tony
Signature

Tony Toews, Microsoft Access MVP
  Please respond only in the newsgroups so that others can
read the entire thread of messages.
  Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

Chris Mills - 16 Mar 2006 19:10 GMT
Although there are some tweaks to the PDW, the PDW is full of "holes". For
example:

-I seem to have avoided the one you mention (and similar) by distributing
latest files.

-It is reasonable to require Access to be to some SP level, but there is no
provision with PDW to do that. Microsoft expects the client to install your
package and then immediately download an SP upgrade (SHEESH)
This is so stupid/inconvenient/laughable for the client, that I wrote and
"published" a method to incorporate SP's into XP PDW. Hereabouts:
(I'm sure it's on the internet but a draft follows at the end of this message)

-There is no provision in PDW to install for multiple signons (ie PrivateGroup
setting and other issues). There was in A2000, but then they changed the
Shellink interface (used to set up icons), introducing further problems when
they fixed others. Some info (for A2000) can be found at
http://www.granite.ab.ca/access/access2000pdwsetup.htm
These fixes only apply to A2000, since MS did not distribute A2002 PDW source
code so you can't change what they did.

-There was a problem (at least in A2000) where PDW requires a reboot, but
Windows XP suppresses the reboot. Nevertheless a reboot is necessary and I
suggest you reboot after installation anyway. Otherwise, you could end up with
the software offering to uninstall itself, as I found when a 30-PC company had
a change-of-shift and everyone signed-on a different way. That was
embarrassing!

-There is no provision in any PDW for a networked install. However that is
reasonable IMHO. What I sometimes do is generate an entirely separate setup
for the data/security file (or anything else which is "common")

-Of course you will have less hassles if you reduce "references" to the
minimum. Don't believe what Microsoft provides by default, take a backup and
try removing references. For instance, I have yet to hear that "OLE
Automation" reference is necessary even if you use OLE Automation!

-For these and many reasons I've forgotten, many people prefer to use the
likes of www.sagekey.com for installations, so at least read what they say
there. I myself still use PDW (my modified 2000 version) with few hassles
really. But the rule-of-thumb is that that's because I am available to my
customers (at least by telephone) to fix up any installations. And they will
surely need some level of "fixing up".

Access PDW was derived from VB PDW, where it was adequate but Access is
obviously more complicated! It was good that Microsoft tried to standardise,
but bad that they never followed through with the requirements to make it
practical. Even some employees of Microsoft have said "oh well, since there
are 3rd party products like sagekey why should we bother" or something to that
effect. I say, Microsoft should have purchased sagekey (wash my mouth out), so
that at least we would have got what we thought we paid for (namely a working
install program)

HTH
Chris
----------
(XP PDW SP fix-up follows. I tested but do not actually use XP PDW)
(Of course, MS PSS should have got off their fat a.ses and provided this)
----------
Patching A2002 Runtime

(recovered from Google)
microsoft.public.access.devtoolkits
Re: Patching Access 2002 Runtime
approx: 2003-08-26
enclosure: Office1.ddf, missing but listed.

Here's how to distribute Access 2002 Runtime SP-2 with your app.
(**Use These Instructions At Your Own Risk**)
(**Take Backups**)

Firstly, get this article on how to build cab's:
HOWTO: Manually Modify and Rebuild CAB Files
http://support.microsoft.com/?id=176810

The essential Access runtime files are contained in Office1.cab, usually
located in "Program Files\Microsoft Office Developer\Access Runtime\1033\ART"

1) Make a working folder C:\NewRuntime and a subfolder Support. Extract all
the files out of Office1.cab into the Support folder. WinZip will do it.

2) Assuming you have Access 2002 SP-2 installed, go though the list of files
in the following article and copy the new files into the Support folder:
Access 2002 Runtime Update:
http://support.microsoft.com/?id=813617

3) Copy the attached Office1.ddf to the Support folder. The file order is
important in this cab-making text-format ddf .

4) Make a new cab:
MakeCab /F Office1.ddf

5) Copy the resulting cab to the mentioned Art folder to have it included in
your packaging.

Chris
(apologies for an enclosure, but it's critical)
---------------------------------------------------------------------------­--
-
Signature

Here's the Office1.ddf text contents for the above instructions, some lines
may wrap:
.Set CabinetName1=Office1.cab
.Set DiskDirectory1=C:\NewRuntime\
.Set Cabinet=on
.Set Compress=on
.Set MaxDiskSize1=0
"C:\NewRuntime\Support\Msacnv30.dll"
"C:\NewRuntime\Support\Msacnv30.exe"
"C:\NewRuntime\Support\Access.pip"
"C:\NewRuntime\Support\Accwiz.dll"
"C:\NewRuntime\Support\Msaccess.exe"
"C:\NewRuntime\Support\Msaexp30.dll"
"C:\NewRuntime\Support\UTILITY.MDA_0001"
"C:\NewRuntime\Support\Acwizrc.dll"
"C:\NewRuntime\Support\Msain.dll"
"C:\NewRuntime\Support\README.TXT_0001"
"C:\NewRuntime\Support\Snapview.exe"
"C:\NewRuntime\Support\Snapview.cnt"
"C:\NewRuntime\Support\Snapshot.chm"
"C:\NewRuntime\Support\Snapview.ocx"
"C:\NewRuntime\Support\Sqlparse.dll"
"C:\NewRuntime\Support\Msacc.olb"
"C:\NewRuntime\Support\Soa.dll"
"C:\NewRuntime\Support\Clntwrap.htm"
"C:\NewRuntime\Support\Rpt2dap.xsl"
"C:\NewRuntime\Support\Rpt2htm4.xsl"
"C:\NewRuntime\Support\Servwrap.asp"
"C:\NewRuntime\Support\Graph10.aw"
"C:\NewRuntime\Support\Mscdm.dll"
"C:\NewRuntime\Support\BIDI32.DLL_0001"
"C:\NewRuntime\Support\INTLDATE.DLL_0001"
"C:\NewRuntime\Support\UCS20.DLL_0001"
"C:\NewRuntime\Support\Mscal.dep"
"C:\NewRuntime\Support\Mscal.ocx"
"C:\NewRuntime\Support\Mscomctl.ocx"
"C:\NewRuntime\Support\Richtx32.ocx"
"C:\NewRuntime\Support\Vsflex3.ocx"
"C:\NewRuntime\Support\Msolap80.dll"
"C:\NewRuntime\Support\Msdmeng.dll"
"C:\NewRuntime\Support\Msdmine.dll"
"C:\NewRuntime\Support\Msdmine.rll"
"C:\NewRuntime\Support\Msolap80.rll"
"C:\NewRuntime\Support\Olapuir.rll"
"C:\NewRuntime\Support\Msmdun80.dll"
"C:\NewRuntime\Support\Msmdcb80.dll_0001"
"C:\NewRuntime\Support\Msmdgd80.dll_0001"
"C:\NewRuntime\Support\Msolui80.dll_0001"
"C:\NewRuntime\Support\GlobalDa.BFA7.7EBEDD31_AA66_11D2_B980_006097C4DE24"
"C:\NewRuntime\Support\GlobalDa.F836.7EBEDD31_AA66_11D2_B980_006097C4DE24"
"C:\NewRuntime\Support\Arbli___.ttf"
"C:\NewRuntime\Support\Ariblk.ttf"
"C:\NewRuntime\Support\Antquab.ttf"
"C:\NewRuntime\Support\Antquabi.ttf"
"C:\NewRuntime\Support\Antquai.ttf"
"C:\NewRuntime\Support\Bkant.ttf"
"C:\NewRuntime\Support\Gothic.ttf"
"C:\NewRuntime\Support\Gothicb.ttf"
"C:\NewRuntime\Support\Gothicbi.ttf"
"C:\NewRuntime\Support\Gothici.ttf"
"C:\NewRuntime\Support\Hatten.ttf"
"C:\NewRuntime\Support\Wingdng2.ttf"
"C:\NewRuntime\Support\Wingdng3.ttf"
"C:\NewRuntime\Support\Fm20.dll"
"C:\NewRuntime\Support\Fm20enu.dll"
"C:\NewRuntime\Support\Graph.exe"
"C:\NewRuntime\Support\Gr9galry.gra"
"C:\NewRuntime\Support\Grintl32.dll"
"C:\NewRuntime\Support\Msrclr40.dll"
"C:\NewRuntime\Support\Msrecr40.dll"
"C:\NewRuntime\Support\Ctryinfo.txt"
"C:\NewRuntime\Support\Mso.dll"
"C:\NewRuntime\Support\Msoicons.exe"
"C:\NewRuntime\Support\Dw.exe"
"C:\NewRuntime\Support\Dwintl.dll"
"C:\NewRuntime\Support\Mso7ftp.exe"
"C:\NewRuntime\Support\Mso7ftpa.exe"
"C:\NewRuntime\Support\Mso7ftps.exe"
"C:\NewRuntime\Support\Msohev.dll"
"C:\NewRuntime\Support\Msohtmed.exe"
"C:\NewRuntime\Support\Msointl.dll"
"C:\NewRuntime\Support\MSIOFF10.MOF_0001"
"C:\NewRuntime\Support\Msioff10.ocx"
"C:\NewRuntime\Support\Offprv10.dll"
"C:\NewRuntime\Support\Offprv10.exe"
"C:\NewRuntime\Support\Msostyle.dll"
"C:\NewRuntime\Support\RICHED20.DLL_0001"
"C:\NewRuntime\Support\UCSCRIBE.DLL_0002"
"C:\NewRuntime\Support\USP10.DLL_0002"
"C:\NewRuntime\Support\Refedit.dll"
"C:\NewRuntime\Support\SAEXT.DLL_0001"
"C:\NewRuntime\Support\Seqchk10.dll"
"C:\NewRuntime\Support\Thdic.lex"
"C:\NewRuntime\Support\Trigram.lex"
"C:\NewRuntime\Support\Wzcnflct.chm"
"C:\NewRuntime\Support\Artsy.elm"
"C:\NewRuntime\Support\Artsy.inf"
"C:\NewRuntime\Support\PREVIEW.GIF_0027"
"C:\NewRuntime\Support\Axis.elm"
"C:\NewRuntime\Support\Axis.inf"
"C:\NewRuntime\Support\PREVIEW.GIF_0028"
"C:\NewRuntime\Support\Blends.elm"
"C:\NewRuntime\Support\Blends.inf"
"C:\NewRuntime\Support\PREVIEW.GIF_0030"
"C:\NewRuntime\Support\Blueprnt.elm"
"C:\NewRuntime\Support\Blueprnt.inf"
"C:\NewRuntime\Support\PREVIEW.GIF_0031"
"C:\NewRuntime\Support\Boldstri.elm"
"C:\NewRuntime\Support\Boldstri.inf"
"C:\NewRuntime\Support\PREVIEW.GIF_0032"
"C:\NewRuntime\Support\Capsules.elm"
"C:\NewRuntime\Support\Capsules.inf"
"C:\NewRuntime\Support\PREVIEW.GIF_0033"
"C:\NewRuntime\Support\Cascade.elm"
"C:\NewRuntime\Support\Cascade.inf"
"C:\NewRuntime\Support\PREVIEW.GIF_0034"
"C:\NewRuntime\Support\Citrus.elm"
"C:\NewRuntime\Support\Citrus.inf"
"C:\NewRuntime\Support\PREVIEW.GIF_0036"
"C:\NewRuntime\Support\Echo.elm"
"C:\NewRuntime\Support\Echo.inf"
"C:\NewRuntime\Support\PREVIEW.GIF_0038"
"C:\NewRuntime\Support\Eclipse.elm"
"C:\NewRuntime\Support\Eclipse.inf"
"C:\NewRuntime\Support\PREVIEW.GIF_0039"
"C:\NewRuntime\Support\Edge.elm"
"C:\NewRuntime\Support\Edge.inf"
"C:\NewRuntime\Support\PREVIEW.GIF_0040"
"C:\NewRuntime\Support\Expeditn.elm"
"C:\NewRuntime\Support\Expeditn.inf"
"C:\NewRuntime\Support\PREVIEW.GIF_0041"
"C:\NewRuntime\Support\Indust.elm"
"C:\NewRuntime\Support\Indust.inf"
"C:\NewRuntime\Support\PREVIEW.GIF_0044"
"C:\NewRuntime\Support\Layers.elm"
"C:\NewRuntime\Support\Layers.inf"
"C:\NewRuntime\Support\PREVIEW.GIF_0046"
"C:\NewRuntime\Support\Level.elm"
"C:\NewRuntime\Support\Level.inf"
"C:\NewRuntime\Support\PREVIEW.GIF_0047"
"C:\NewRuntime\Support\Network.elm"
"C:\NewRuntime\Support\Network.inf"
"C:\NewRuntime\Support\PREVIEW.GIF_0051"
"C:\NewRuntime\Support\Pixel.elm"
"C:\NewRuntime\Support\Pixel.inf"
"C:\NewRuntime\Support\PREVIEW.GIF_0053"
"C:\NewRuntime\Support\PREVIEW.GIF_0056"
"C:\NewRuntime\Support\Profile.elm"
"C:\NewRuntime\Support\Profile.inf"
"C:\NewRuntime\Support\PREVIEW.GIF_0057"
"C:\NewRuntime\Support\Quad.elm"
"C:\NewRuntime\Support\Quad.inf"
"C:\NewRuntime\Support\PREVIEW.GIF_0058"
"C:\NewRuntime\Support\Radial.elm"
"C:\NewRuntime\Support\Radial.inf"
"C:\NewRuntime\Support\PREVIEW.GIF_0059"
"C:\NewRuntime\Support\Refined.elm"
"C:\NewRuntime\Support\Refined.inf"
"C:\NewRuntime\Support\PREVIEW.GIF_0060"
"C:\NewRuntime\Support\Ricepapr.elm"
"C:\NewRuntime\Support\Ricepapr.inf"
"C:\NewRuntime\Support\PREVIEW.GIF_0061"
"C:\NewRuntime\Support\Rmnsque.elm"
"C:\NewRuntime\Support\Rmnsque.inf"
"C:\NewRuntime\Support\PREVIEW.GIF_0063"
"C:\NewRuntime\Support\Strtedge.elm"
"C:\NewRuntime\Support\Strtedge.inf"
"C:\NewRuntime\Support\PREVIEW.GIF_0064"
"C:\NewRuntime\Support\Studio.elm"
"C:\NewRuntime\Support\Studio.inf"
"C:\NewRuntime\Support\PREVIEW.GIF_0065"
"C:\NewRuntime\Support\Sumipntg.elm"
"C:\NewRuntime\Support\Sumipntg.inf"
"C:\NewRuntime\Support\Themes.inf"
"C:\NewRuntime\Support\PREVIEW.GIF_0067"
"C:\NewRuntime\Support\Watermar.elm"
"C:\NewRuntime\Support\Watermar.inf"
"C:\NewRuntime\Support\Mscal.cnt"
"C:\NewRuntime\Support\Mscal.hlp"
"C:\NewRuntime\Support\Grtip10.hlp"
"C:\NewRuntime\Support\Graph10.chm"
"C:\NewRuntime\Support\Vbagr10.chm"
"C:\NewRuntime\Support\Owcrdp10.chm"
"C:\NewRuntime\Support\Owcdpl10.chm"
"C:\NewRuntime\Support\Owcrpl10.chm"
"C:\NewRuntime\Support\Owcvba10.chm"
"C:\NewRuntime\Support\Owcdss10.chm"
"C:\NewRuntime\Support\Owcrss10.chm"
"C:\NewRuntime\Support\Owcdch10.chm"
"C:\NewRuntime\Support\Owcrch10.chm"
"C:\NewRuntime\Support\Owcfun10.chm"
"C:\NewRuntime\Support\Vbacv10.dll"
"C:\NewRuntime\Support\Vbacv10d.dll"
"C:\NewRuntime\Support\Vbacv20.dll"
"C:\NewRuntime\Support\Vbe6.dll"
"C:\NewRuntime\Support\Vbe6ext.olb"
"C:\NewRuntime\Support\Vbe6intl.dll"
"C:\NewRuntime\Support\Ven2232.olb"
"C:\NewRuntime\Support\Vbaend32.olb"
"C:\NewRuntime\Support\Vbaen32.olb"
"C:\NewRuntime\Support\Msaddndr.dll"
"C:\NewRuntime\Support\Vbame.dll"
"C:\NewRuntime\Support\Scp32.dll"
"C:\NewRuntime\Support\Msstdfmt.dll"
"C:\NewRuntime\Support\Msstkprp.dll"
"C:\NewRuntime\Support\Owc10.dll"
"C:\NewRuntime\Support\Owci10.dll"
"C:\NewRuntime\Support\D3d7nt4.dll"
"C:\NewRuntime\Support\Dd7nt4.dll"
"C:\NewRuntime\Support\Msowcf.dll"
"C:\NewRuntime\Support\Mce.dll"
"C:\NewRuntime\Support\Mceintl.dll"
"C:\NewRuntime\Support\Ocp.dll"
"C:\NewRuntime\Support\Ocp.sll"
"C:\NewRuntime\Support\Ocpintl.dll"
"C:\NewRuntime\Support\msxml3.dll.35210702_493B_42CA_BA13_865C5A8BDAC1"
"C:\NewRuntime\Support\msxml3a.dll.35210702_493B_42CA_BA13_865C5A8BDAC1"
"C:\NewRuntime\Support\msxml3r.dll.35210702_493B_42CA_BA13_865C5A8BDAC1"
"C:\NewRuntime\Support\vsansidl.2BF3.3643236F_FC70_11D3_A536_0090278A1BB8"
"C:\NewRuntime\Support\msddsdll.CAB3.3643236F_FC70_11D3_A536_0090278A1BB8"
"C:\NewRuntime\Support\msddsuid.C87E.3643236F_FC70_11D3_A536_0090278A1BB8"
"C:\NewRuntime\Support\msddsfdl.2BF3.3643236F_FC70_11D3_A536_0090278A1BB8"
"C:\NewRuntime\Support\msddslmd.221A.3643236F_FC70_11D3_A536_0090278A1BB8"
"C:\NewRuntime\Support\vdt70uid.C87E.3643236F_FC70_11D3_A536_0090278A1BB8"
"C:\NewRuntime\Support\vdt70dll.CAB3.3643236F_FC70_11D3_A536_0090278A1BB8"
"C:\NewRuntime\Support\mdt3gdll.CAB3.3643236F_FC70_11D3_A536_0090278A1BB8"
"C:\NewRuntime\Support\msvcp70d.221A.3643236F_FC70_11D3_A536_0090278A1BB8"
"C:\NewRuntime\Support\msvcr70d.221A.3643236F_FC70_11D3_A536_0090278A1BB8"
-----end-----

George Nicholson - 16 Mar 2006 22:15 GMT
Thanks a lot, Chris

Rebuilding the cab with the most recent files is what I really wanted to do
but wasn't entirely sure how. I feel better about attempting it with your
blow-by-blow.

Signature

George Nicholson

Remove 'Junk' from return address.

> Although there are some tweaks to the PDW, the PDW is full of "holes". For
> example:
[quoted text clipped - 115 lines]
> ---------------------------------------------------------------------------­--
> -
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.