If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Error #1321 MOS 2003 Setup
MOS 2003 Pro install setup error on Win XP Pro SP1. I was having trouble
getting the BCM add-in to associate with OL 2003. I was asked to uninstall BCM and MOS 2003 Pro and then to reinstall MOS 2003. MOS 2003 was working fine. With support help from MSFT Office specialist (not Convergys) we meticulously deleted the appropriate reg keys and files. We were going to use the Windows Installer Cleanup Utility, but it didn't list MOS 2003 so we did it manually. http://support.microsoft.com/default...b;en-us;290301 I am getting the following setup errors and setup stops when trying to install wisptis.exe. Wisptis.exe is unfortunately installed with MOS and it works with tablet PC. If you don't have a tablet, it stubbornly starts and helps itself to CPU. Just ending it as a process or trying to use msconfig won't stop it. A CPU gobbler that far and away most of the population dosn't need as a gift from the MOS developers and product team with every Office installation is ridiculous, but someone at Redmond made that call. These two links context how to get rid of it and I used one of these tools. They work and wisptis.exe disappears from your procdesses. Now I think this is causing me problems on the reinstall. I took steps here to uninstall wisptis.exe: http://www.boredguru.com/modules/new...d=193&forum=24 I'm getting this Error: Error 1321: Setup cannot modify the file C:\Config.MSI 3a5322.rbf. Verify that the file exists (it doesn't) in your system and that you have sufficient permission to update it. Should I search for this to download it? Could it possibly have been eliminated iin getting rid of the wisptis.exe annoyance? http://support.microsoft.com/default...b;en-us;232143 This KB deals with the error in Office XP and recommends checking a registry value here. My value is correct and conforms with this solution: HKEY_Local_Machine/Software/Microsoft/Windows NT/CurrentVersion/Winlogon 1.. In the right pane, right-click AllocateCDRoms, and then click Modify. 2.. In the Value data box, type 0 (zero), and then click OK. 3.. Would appreciate if anyone has suggestions as to how to overcome this setup error. TIA, Chad Harris |
#2
|
|||
|
|||
How I Fixed 1321 Setup Error and Setup a Defense Against Mandatory MSFT Wisptis Installation (Malware)
I truly appreciate the high quality of help that MS MVPs and others
unselfishly on the Office/Outlook groups day after day that allows you to get a lot of valuable links and between the lines help/ learning to supplement books. The greatest thing about having used the Wisptis removal tool is that once you overcome the setup problem--MSFT doing anything it can to get wisptis.exe in for the tablet PC--you have what I call the Star Wars Defense Against Redmond Office Developer Bad Judgment--and you'll get the chance f to ignore wisptis.exe a potential CPU gobler freezer--the Redmond MSFT version of spyware with "rich, robust, functionality": I finally got it in and without the @@@###$$%%%%% Redmond wisptis.exe and your links pushed me to keep trying. 1) I blew off Norton. 2) I used a Beta RC1 MSI 3.0 installer. 3) I got a 1911 error that gave me the chance to say no to wisptis and I got my Office back. Here's what I take away from this. I installed MOS 2003 two or three times and paid no attention to Norton but from now on I'll always shut it down during Office and major installations or installations that are having problems getting in that I can detect. The MSI or Windows Installer has always had problems, and if you're encountering stubborn set up errors like this one, anything you can do to repair or get a new installer may get the job done. BTW--Whisptis.exe is not the only ill-conceived .exe to completely escape Beta testing. And I can appreciate that wisptis although not needed by 99+% of Office users may not be causing problems, but when it is keeping you from installing Office because you got rid of it that takes on a whole new dimension. Note this by Sam Gentile (experienced engineer, .net developer and author on .net since it's inception on his blog: Outlook 2003 Causing CRSS.EXE to go spastic! http://samgentile.com/blog/archive/2.../15/11186.aspx I have been spending so much time trying to get Office in the last few days, that I was pretty burned out but when you stuck with it I decided to give it one more try. I know set up problems aren't that interesting to people unless it's their own and installers aren't by a long shot the most satisfying part of Office or Windows obviously, but when you need them they become important. It's not near as much fun as clip art can be, but without Office you aren't using Office clip art. So thanks for sticking with it and stretching to get some good resources that I still want to learn about. Obviously Install Shield had a way to log installs (and that made me think of Verbose logging as well) and in the right hands that could produce the info you need I imagine. Here's what it did and I have my MSO 2003 back working well. Whether MSFT knows how to get in their BCM remains to be seen. I think they have the developers for that add-in hidden better than WMD in/out of Iraq. I still am going to pursue the answers to my questions but one in a sense did get answered. 1) I decided since every single experienced Office user, MVPs and MSFT Office people are unanimous in saying that Norton can definitely interfere with Office installations in particular to nuke Norton off my computer. 2) I decided maybe I needed some new blood in my installer. Because, and I don't know and want to find out how experienced Office set up people would describe this but my errors may have indicated components of the MSI itself were missing, or that .dlls that the installer writes to or calls on or invokes including the many C:\config.msi.rbf numbered files invoked in the errors were missing. I had mentioned to you and I've seen the concept batted in XP newsgroups, that maybe I could download the MSI http://www.microsoft.com/downloads/d...2-DE3BB768148F but if I remember correctly, you can update for 95, 98, ME or what people call the MSFT Wintendo OS's, but XP contains the correct installer--2.0 and XP SP2 contains the Betas I believe of 3.0 and I suppose they will dovetail MSI 3.0 for the XP SP2 RTM. This is the quote on the link above. I was thinking that you might be able to find the download for Windows Installer 2.0 and refresh the files. That's also what I attempted to do when I ran System File Checker last night and it didn't help. I was trying desperately to fix the installer or give the installer any of the C:\Config.msi files it needed that were damaged or missing by running SFC. "Windows XP contains Windows Installer 2.0 and therefore can't be installed or upgraded by this redistributable." *So that raises the question how does one fix MSI 2.0 in Windows XP if they need to to install whatever Office included?* So I decided to use and I'm not discussing it I'm just saying I used it the Beta MSI 3.0 crossing my fingers it would help me. I knew it might complicate things but I could always blow it off. I plan to put that question on the XP Customize group because I may be able to draw an answer there or if there is an XP setup group or an MSDN group where I can get it answered so much the better. 3) Then I ran MOS 2003 set up. I got this error and this is one of my favorite error experiences. I betcha the GUID referenced is the GUID for the Tablet PC ink component, the little CPU gobbler that MSFT Office developers have so generously shoved down the throat of anyone who installs MSFT Office whether they plan to touch a tablet PC or not. And it's not that I don't think tablets will be a definite part of many verticals, schools, and companies and have lots of potential, its just that MSFT has no business sticking a little used file that can cause serious CPU freezes for such a little utilized purpose when they could make it optional. And after all, since both wisptis.exe can "freak" your CPU as well as In connection with the 1911 error below I got what is my favorite dialogue box of the year. Doyawanna retry or doyawanna ignore? And it was there that I found my holy grail that I'd been looking for--how to install MOS 2003 and surgically blow off the infamous trouble maker wisptis.exe. I hit IGNORE and the installation zoomed right on without it and installed successfully. Product: Microsoft Office Professional Edition 2003 -- Error 1911. Setup cannot register type library for file C:\WINDOWS\System32\WISPTIS.EXE. Contact Microsoft Product Support Services (PSS) for assistance. For information about how to contact PSS, see G:\FILES\PFILES\MSOFFICE\OFFICE11\1033\PSS10R.CHM. Detection of product '{91E30409-6000-11D3-8CFE-0150048383C9}', feature 'HandWritingFiles' failed during request for component '{E6BFD503-3A35-4B78-BAB5-9570EDDEF81C}' Product: Microsoft Office Professional Edition 2003 -- Installation operation completed successfully. Product: Microsoft Office Professional Edition 2003 -- Configuration completed successfully. So thanks very much for the help Mary. I hate the time these MSFT Windows and Office problems can take, but putting things together and solving them is a sweet feeling--and you hope you're a little bit better able to handle the next similar one because it's just around the corner. I want to thank Office MVP Mary Sauer http://www.mvps.org/msauer/ for posting this possible help for a 1321 setup error so I'm passing it on here in the setup forum: Do you have Norton? Disable "Script Blocking" and in options, disable Office Plug-ins before you install. This document is for 2000 but it addresses your issue Various Error Messages When MSI File Creates and Modifies Files and Registry Keys http://support.microsoft.com/default...b;en-us;232143 http://www.appdeploy.com/faq/msi_err...tail.asp?id=84 Have you tried cleaning up the Installer? Description of the Windows Installer CleanUp Utility http://support.microsoft.com/default...roduct=off2003 There is a knowledge base article that may relate. Office 2003 Install May Fail When You Use a Transform File http://support.microsoft.com/default...roduct=off2003 When you open Norton, near the top is the options button, this is where you disable office plug-ins. In my opinion Norton should be disabled altogether before you install. Installshield has some documents too ERRDOC: Windows Installer Error 1321 http://support.installshield.com/kb/...icleid=Q107388 I have wisptis on my computer, it was installed when I installed Office. I also have Adobe 6, but doing a search on my computer does not have show evidences of it being part of Adobe. Have you setup a log? How to use an Office 2003 Setup log file to troubleshoot Setup problems http://support.microsoft.com/default.aspx?kbid=826511 Yours is a rare error... if you ever get it worked out let me know. I wish I could be more help. Hopefully someone will jump in here and solve it for you. -- Mary Sauer MS MVP http://office.microsoft.com/ http://www.mvps.org/msauer/ news://msnews.microsoft.com Watchout for files that can freeze your computer that should have been optional add-ins that Office Developers have made mandatory. This is a quintissential example: Wisptis,exe is installed with every Office 2003 application including One Note SP1 trial and in the future One Note SP1 possibly with Adobe Acrobat 6.0. After you run one of the removal tools on the web, you may have to get a new installer to Install Office as I did so take the best measure which is to right click on the file C:\windows\system32\wisptis.exe, click Properties, go to the security taband remove all permissions except An easier way to do it is to right click on the file C:\windows\system32\wisptis.exe, click Properties, go to the security tab and remove all permissions except for Read permissions.You'll never see it run again. I wanted to be able to use a tool to custom install and surgically excerpt Wisptis from my install so I could now get Office in. Once I replaced my installer, I was able to tell setup to ignore what is tantamount to malware that the Office 2003 development team in conjunction with the tablet boys and girls sought to make you install in every Office application--wisptis.exe. Does anyone know the percent of legitimate office copy users who also need wisptis for a tablet PC--how low a fraction of 1% could it be? Another example of buggy Office 2003 interaction with Windows files is: "Outlook 2003 Causing CRSS.EXE to go spastic" http://samgentile.com/blog/archive/2.../15/11186.aspx What's wisptis--You have it!!!! It's an unwelcome gift from the Office Development Team with Office 2003! *What Wisptis is--among other things, certainly not needed in Micorosft Office--it should have been an optional download.* I have long ago given up on trying to figure out the answer to "What were they thinkiing?" when it comes to developers or Product Teams on the Redmond campus. "Let's put in a pen data collection component for Tablet PC whether anyone has a tablet or not. It'll serve as a great memory hog with excellent potential to freeze computers and send CPU to 100%!!! But let's not tell anyone this can happen. Let them be surprised." http://216.239.57.104/search?q=cache...ptis.exe&hl=en Wisptis.exe (\Windows\System32) This executable runs as a system service that provides pen-data collection for other components of the SDK. When a component needs to interact with the pen (for example, to collect ink or to detect gestures), this executable is spawned as a service to communicate directly with the input device. On a Tablet PC, Wisptis.exe interacts with the digitizer, whereas on a desktop it interacts with the mouse as well. The executable’s name is an acronym that references an outdated internal name for the team that developed it (Windows Ink Services Platform Tablet Input Subsystem). Notes on the web on wisptis--what's not known is the extent to which it is malwa Well I don't have a Tablet PC and I certainly don't want an unnecessary process eating up my memory resources. You cannot get rid of wisptis.exe by renaming or deleting it: Windows File Protection would cause it to reinstall the next time you run Adobe Acrobat. There is even a rumor about a bug in wisptis.exe itself whereby it keeps part of the current user registry hive locked, preventing updates and eventually resulting in a corruption of the registry hive (which as reported leads to a "Userenv event 1517" on logging off or shutting down). Others reported GDI leaks and CPU hogging. I haven't noticed the latter but can confirm that at one point, the number of open GDI handles by wisptis.exe was above 1000, which is unacceptable. So by and large it seems wisptis.exe can make a thorough nuisance of itself. To uninstall wisptis and Microsoft's Tablet PC Components on your PC, you must delete the following registry entries: HKEY_CLASSES_ROOT\AppID\{7F429620-16D1-471E-A81A-114992148034} HKEY_CLASSES_ROOT\AppID\wisptis.EXE HKEY_CLASSES_ROOT\CLSID\{04A1E553-FE36-4FDE-865E-344194E69424} HKEY_CLASSES_ROOT\CLSID\{13DE4A42-8D21-4C8E-BF9C-8F69CB068FCA} HKEY_CLASSES_ROOT\CLSID\{242025BB-8546-48B6-B9B0-F4406C54ACFC} HKEY_CLASSES_ROOT\CLSID\{3336B8BF-45AF-429F-85CB-8C435FBF21E4} HKEY_CLASSES_ROOT\CLSID\{3EE60F5C-9BAD-4CD8-8E21-AD2D001D06EB} HKEY_CLASSES_ROOT\CLSID\{43B07326-AAE0-4B62-A83D-5FD768B7353C} HKEY_CLASSES_ROOT\CLSID\{43FB1553-AD74-4EE8-88E4-3E6DAAC915DB} HKEY_CLASSES_ROOT\CLSID\{524B13ED-2E57-40B8-B801-5FA35122EB5C} HKEY_CLASSES_ROOT\CLSID\{632A2D3D-86AF-411A-8654-7511B51B3D5F} HKEY_CLASSES_ROOT\CLSID\{65D00646-CDE3-4A88-9163-6769F0F1A97D} HKEY_CLASSES_ROOT\CLSID\{6E4FCB12-510A-4D40-9304-1DA10AE9147C} HKEY_CLASSES_ROOT\CLSID\{786CDB70-1628-44A0-853C-5D340A499137} HKEY_CLASSES_ROOT\CLSID\{836FA1B6-1190-4005-B434-7ED921BE2026} HKEY_CLASSES_ROOT\CLSID\{8770D941-A63A-4671-A375-2855A18EBA73} HKEY_CLASSES_ROOT\CLSID\{8854F6A0-4683-4AE7-9191-752FE64612C3} HKEY_CLASSES_ROOT\CLSID\{937C1A34-151D-4610-9CA6-A8CC9BDB5D83} HKEY_CLASSES_ROOT\CLSID\{9C1CC6E4-D7EB-4EEB-9091-15A7C8791ED9} HKEY_CLASSES_ROOT\CLSID\{9DE85094-F71F-44F1-8471-15A2FA76FCF3} HKEY_CLASSES_ROOT\CLSID\{9FD4E808-F6E6-4E65-98D3-AA39054C1255} HKEY_CLASSES_ROOT\CLSID\{A5558507-9B96-46BA-94ED-982E684A9A6B} HKEY_CLASSES_ROOT\CLSID\{A5B020FD-E04B-4E67-B65A-E7DEED25B2CF} HKEY_CLASSES_ROOT\CLSID\{AAC46A37-9229-4FC0-8CCE-4497569BF4D1} HKEY_CLASSES_ROOT\CLSID\{C52FF1FD-EB6C-42CF-9140-83DEFECA7E29} HKEY_CLASSES_ROOT\CLSID\{D8BF32A2-05A5-44C3-B3AA-5E80AC7D2576} HKEY_CLASSES_ROOT\CLSID\{DE815B00-9460-4F6E-9471-892ED2275EA5} HKEY_CLASSES_ROOT\CLSID\{E3D5D93C-1663-4A78-A1A7-22375DFEBAEE} HKEY_CLASSES_ROOT\CLSID\{E5CA59F5-57C4-4DD8-9BD6-1DEEEDD27AF4} HKEY_CLASSES_ROOT\CLSID\{E9A6AB1B-0C9C-44AC-966E-560C2771D1E8} HKEY_CLASSES_ROOT\CLSID\{EFB4A0CB-A01F-451C-B6B7-56F02F77D76F} HKEY_CLASSES_ROOT\CLSID\{F0291081-E87C-4E07-97DA-A0A03761E586} HKEY_CLASSES_ROOT\Installer\Components\BCA32ECD550 E1F4488DBD2A1578ACF8B HKEY_CLASSES_ROOT\Installer\Features\7040110900063 D11C8EF10054038389C\WISPFiles HKEY_CLASSES_ROOT\Installer\Features\7040110900063 D11C8EF10054038389C\WISPHidden HKEY_CLASSES_ROOT\TpcCom.* (all of them) HKEY_CLASSES_ROOT\TypeLib\{194508A0-B8D1-473E-A9B6-851AAF726A6D} HKEY_CLASSES_ROOT\TypeLib\{56D04F5D-964F-4DBF-8D23-B97989E53418} HKEY_CLASSES_ROOT\TypeLib\{773F1B9A-35B9-4E95-83A0-A210F2DE3B37} HKEY_CLASSES_ROOT\TypeLib\{7D868ACD-1A5D-4A47-A247-F39741353012} HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Components\1125549C421D34E4DBF1036F62 580BE1 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Components\652A08B235C6DFF4C8CD41B52D E68CA4 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Components\9B4B5940D4625D64C85532B8CD E3BF4D HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Components\D656DA4A9E277A34D90D5E6FFA 34E827 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\7040110900063D11C8EF10054038 389C\Featu res\WISPFiles HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Installer\UserData\S-1-5-18\Products\7040110900063D11C8EF10054038 389C\Featu res\WISPHidden Now you can also safely delete \Windows\System32\Wisptis.exe. Make sure the process is not running; otherwise kill it before deletion. __________________________________________________ __________________________ ____________________________________________ *My Lack of MSFT Support Rant and View Hex Error Messages Do Nothing for the User to Solve a Problem in Real Time so why offer them to the User?* I was also running SP2 at the time as a Beta tester, and even though I had tried to associate BCM before with SP2 uninstalled and going back to SP1, they wanted to work with SP2 off. I don't believe that SP2 is the problem with associating that desktop SQL MSDE with Outlook. I think it has more to do with the fact that it's the first .net add in MSFT has had and they pushed it out unfinished with a lot of problems as a fairly buggy Beta but they called it RTM. No big precedent there--it happens with all their software to degrees and certainly happens with the Windows OS and Office and will be the case with Longhorn and Blackcomb. So here is this company who is going to spend $300 million dollars to promote XP SP2 because they want way more than 250 million legitimate copies sold--if SP2 is radically different someone wake me up because I've read everything MSFT has written on it. It baby sits and reminds people to use a firewall and update viral definitions some of whom are much more concerned about the latest Kazaa lite fileshare. That's why some of the best and brightest universities in the US become viral infected every single day. My point here is that this company that I like is going to spend this huge amount of money promoting SP2--but they are telling me that they don't think an Office component out of a $500 box of Office is compatible with what they are feverishely trying to get on every OEM computer and the OEM companies are perenially like somoene who is thirsty in the desert--they want moisture and they aren't particularlly worried about whether the water is safe or not. Anything that even hints of a new OS wrinkle the OEMs always push for. You don't have to be a NYT, WSJ, IBD afficianado to get that. I think one add campaign I won't see from whoever handles the promotion is "Watchout!!!! Don't buy Office because SP2 won't work with one of the CD's in Office Pro or Office Enterprise edition. We are recalling Office because of SP2. SP2 isn't the problem with BCM, but it's a good excuse for Convergys to say we don't support a Beta when they don't know anything about the Office add-in BCM and they don't. But once SP2 releases to manufacture with the major problem that it's not compatible with Norton Internet Security or Norton System Works, and RC1 is public now being promoted on TechNet's site as a download, so I am perfectly OK in saying that using Norton will evoke screens that say it's not compatible with SP2 builds (all of them). It must be further than I thought from Redmond Washington to Cupertino California and I suppose MSFT is not allowed to use Live Meeting or even Net Meeting that's still in XP by putting "conf" in the run box, or a cell phone, or email out of Redmond to communicate with Symantec Enterprise/Norton Home and Small Business users to iron out the kinks. It won't be the first time. And I know for a fact they've heard from plenty of people using SP2 on this. At this time I want to point out how much help the all hex all the time error messages are for the consumer or even the Sys Ad maven. Few people have the tools and training to interpret these hex errors, so they are zero help to most of us. The site .oca.microsoft.com the so-called crash analysis site is completely and utterly worthless--I've played with it for three years and never seen it yield anything but that there's no solution for any given error at this time. What they're thinking with it I don't know. I have heard people from Redmond speak of real time practical error help about the time Longhorn every births, but Longhorn ain't no short term solution and it's a different vision depending on what side of the bead Mr. Allchin wakes up on. Right now helpful error messages are in the primitive stages. Many of the KBs have little or no help and I've read a few thousand, and many are superficial brushes by the subject like the single one on the 1321 error with its reference to one registry key. __________________________________________________ ___ *I mean MSFT because I want to be clear that Convergys can't and doesn't support BCM. Its employees doesn't know anything about BCM and by and large the phone support for MSFT is from Convergys employees, many of whom want to keep it an NSA secret that they work for Convergys. I'd be hiding as well if I were Convergys. They have a compelling reason to hide and MSFT has a compelling reason to hide that they farm support out to them. So I persisted in asking for help from MSFT. Call me silly. I believed the Redmond company that makes and develops and writes code for the product and sells it at quite a profit and lives quite well because of these sales should actually support the product. Likewise the Convergys support route knows next to nothing about Office setup problems as well but they call themselves "set up specialists" much like a degree mill where you can buy a Ph.D. in whatever field over the web in seconds and call yourself Dr. Bozo. Chad Harris __________________________________________________ __________________________ ___________________________________________ "Chad Harris" wrote in message ... MOS 2003 Pro install setup error on Win XP Pro SP1. I was having trouble getting the BCM add-in to associate with OL 2003. I was asked to uninstall BCM and MOS 2003 Pro and then to reinstall MOS 2003. MOS 2003 was working fine. With support help from MSFT Office specialist (not Convergys) we meticulously deleted the appropriate reg keys and files. We were going to use the Windows Installer Cleanup Utility, but it didn't list MOS 2003 so we did it manually. http://support.microsoft.com/default...b;en-us;290301 I am getting the following setup errors and setup stops when trying to install wisptis.exe. Wisptis.exe is unfortunately installed with MOS and it works with tablet PC. If you don't have a tablet, it stubbornly starts and helps itself to CPU. Just ending it as a process or trying to use msconfig won't stop it. A CPU gobbler that far and away most of the population dosn't need as a gift from the MOS developers and product team with every Office installation is ridiculous, but someone at Redmond made that call. These two links context how to get rid of it and I used one of these tools. They work and wisptis.exe disappears from your procdesses. Now I think this is causing me problems on the reinstall. I took steps here to uninstall wisptis.exe: http://www.boredguru.com/modules/new...d=193&forum=24 I'm getting this Error: Error 1321: Setup cannot modify the file C:\Config.MSI 3a5322.rbf. Verify that the file exists (it doesn't) in your system and that you have sufficient permission to update it. Should I search for this to download it? Could it possibly have been eliminated iin getting rid of the wisptis.exe annoyance? http://support.microsoft.com/default...b;en-us;232143 This KB deals with the error in Office XP and recommends checking a registry value here. My value is correct and conforms with this solution: HKEY_Local_Machine/Software/Microsoft/Windows NT/CurrentVersion/Winlogon 1.. In the right pane, right-click AllocateCDRoms, and then click Modify. 2.. In the Value data box, type 0 (zero), and then click OK. 3.. Would appreciate if anyone has suggestions as to how to overcome this setup error. TIA, Chad Harris |
Thread Tools | |
Display Modes | |
|
|