
alman84
MemberContent Type
Profiles
Forums
Events
Everything posted by alman84
-
Thanks for the replies! We've already ordered new monitors, but we're keeping the old monitors to see if we can fix them anyway. I popped open one of the monitors about a week ago, but I didn't really do much investigative work - just re-connected the ribbons and wires. That capacitor info is kind of disheartening - of course, I should expect something like that from Dell We've got a soldering iron here in the office, and if we find that's the problem, replacing them will of course be easy. Again, thanks for the suggestions.
-
Nothing - I actually plugged the monitor in on my tool workbench (away from the other monitor) and still got the stripes, but only after plugging in a VGA cable. I'm guessing that means there's something wrong with the VGA internals, but taking the whole thing apart didn't help. I just 2x checked all connections and didn't see anything out of the ordinary, but I've still got the stripe. We ordered some new monitors so I think we're just gonna throw it away. It was worth a try - it was a nice monitor. Thanks for the suggestions guys.
-
Found this http://www.fixya.com/support/t139781-pink_stripe Gonna give that a try, anyone taken apart a Dell monitor before?
-
Took me a while to find it, but I'm downloading and trying it now EDIT: I tried that, but it didn't work. That would make sense because I get the stripe even when there's no input (like if I switch the monitor input to S-Video, the screen is black but the stripe is still there even though there's no source)
-
Hey all, The office I work in has had a few Dell monitors start doing the exact same thing. I took a picture to show: Any idea? I can only think of it being something like a faulty decoder. I know it's not the computer or cable as I've tried switching both to no avail, plus it's happened on three different monitors (the exact same model - Dell 2100 FPV). I'm kind of thinking we're just going to have to buy new ones (they're not under warranty anymore), but thought I'd see if anyone knew what was wrong and if it was repairable. Thanks
-
Winsxs folder is HUGE!?
alman84 replied to x-Shadow-x's topic in Unattended Windows Vista/Server 2008
I can verify this. I was running out of HD space on some older machines that I put Vista on and stripping the languages works wonders. -
SpyBot Search & Destroy 1.52 Completly Silent Install
alman84 replied to cardguy1000's topic in Application Installs
Why not just use a /silent or /verysilent switch? Both of those work with spybot 1.52. There are some config changes that I personally made so after it installs I just copy a custom made .ini file to the program directory. Can't verify that the code in the OP works but if someone is reading this and needs an alternative to the script, this is always an option. (for those wondering, it's "Default configuration.ini" and it just goes in the main program file directory for spybot: [Main] EasyMode=1 Legals=0 ShowDetails=1 AutoSave=1 CreateBackups=1 CreateTrackBackups=1 CreateSystemBackups=1 CreateSystemRestorePointSpyware=0 CreateSystemRestorePointInternals=0 IgnoreIncludeFileError=1 Confirmation=1 Compability=1 Priority=Normal RecoveryAged=1 [Main\AlertSounds] AlertSpyFound=0 AlertNothingFound=0 [Automation\ProgramStart] AutoCheck=1 AutoFix=1 RerunAfterFix=0 AutoImmunize=0 DontAsk=1 WaitStart=0 WaitPrograms=0 WaitMore=0 [Automation] SystemStart=NoAutomation [Automation\SystemStart] AutoCheck=1 AutoFix=1 WaitStart=0 WaitPrograms=0 WaitMore=0 AutoClose=0 [Automation\WebUpdate] AutoCheck=0 AutoDownload=1 RemindUpdate=0 CheckBetas=0 CheckAllLanguages=0 CheckSkins=0 CheckSignatures=0 UseProxy=0 [Logfile] WriteCheckLog=1 WriteFixLog=1 IncludeLogDetails=1 OverwriteLog=0 [Look] BlindUser=0 DisplayHeader=1 InfoPanelHighlight=0 [BugReport] UseDefaultMailer=1 IncludeSysInfo=1 IncludeResults=1 IncludeActiveX=1 IncludeBHO=1 IncludeBrowserPages=1 IncludeProcessList=1 IncludeStartup=1 IncludeWinsockLSPs=1 IncludeClipboardText=0 IncludeClipboardImage=0 IncludeSpyFiles=0 CarbonCopy=1 [Expert] ShredTracks=1 ShredRecovery=1 ShowResultsButtons=0 ShowRecoveryButtons=0 [Expert\Viewer] HelperUseFiles=0 HelperUseFolders=0 HelperUseRegistry=0 [Filesets] Spybot - Search & Destroy=1 Security.sbi=1 Malware.sbi=1 QA Tests.sbi=1 Trojans.sbi=1 Hijackers.sbi=1 Keyloggers.sbi=1 Cookies.sbi=1 LSP.sbi=1 Dialer.sbi=1 Temporary.sbi=1 Spybots.sbi=1 Revision.sbi=1 [Durations] Spybot - Search & Destroy=0 Security.sbi=0 Malware.sbi=0 QA Tests.sbi=0 Trojans.sbi=0 Hijackers.sbi=0 Keyloggers.sbi=0 Cookies.sbi=0 LSP.sbi=0 Dialer.sbi=0 Temporary.sbi=0 Spybots.sbi=0 Revision.sbi=0 Gebrauchsspuren=0 Tracks.uti=0 [Tools.Visibility] aToolsHosts=0 aOnlineOptOut=0 aToolsViewReport=1 aOnlineBugReport=0 aToolsShredder=1 aToolsResident=1 aToolsActiveX=0 aToolsBHOs=0 aToolsBrowserPages=0 aToolsIETweaks=1 aToolsProcessList=0 aToolsSystemInternals=1 aToolsRun=1 aToolsWinsock=1 -
If the batch file is in the same directory as your exe, the syntax I posted is right. It depends on where you want to store the exe. If it's on your CD, you don't need to extract firefoxinstall.exe to anything, you can just run it. If you want to specify within your batch file the location of firefoxinstall.exe, you'll have to do something like this: "C:/<directory locations>/firefoxinstall.exe" -ms which will do the same thing.
-
Not sure if I'm understanding correctly, but you should just need to know the location of your .exe or .msi (and keep the required installation files with it). So if you're creating a CD that installs Firefox silently, all you'd need is a "firefox_install.bat" (or whatever you want to call it) and firefoxinstall.exe and the batch file would read like this: firefoxinstall.exe -ms (since -ms is the firefox switch for silent install) Not sure if that helped, I'm more than happy to help more if you can maybe specify a little bit?
-
Thanks for the replies! hiro1, How does that bypass the EULA? Yesterday after I posted this I edited my batch file execution to this: start /wait msiexec /qr /norestart /i openofficeorg24.msi SELECT_WORD=1 SELECT_EXCEL=1 SELECT_POWERPOINT=1 COMPANYNAME="DSH" ADDLOCAL=ALL which, if I'm not mistaken, does pretty much the same as your batch file? I'm still relatively new to network management so I'm probably missing something. Also anonymous_user, thanks for the input. I tried doing some things (like "EULA=1" and whatnot), but I still got the EULA and other business on first start. Now I'm sort of answering my own question, but I did some further investigating and found the files that determine whether or not the EULA and settings are shown on start. They're located in the "Documents and Settings\<userprofile>\Application Data\OpenOffice.org2\user\registry\data\org\openoffice" directory. There are two files - Setup.xcu and UserProfile.xcu. These contain the settings and boolean checks which determine whether or not the FirstStartWizard is launched If you just replace these files with the following, it won't ask for anything on first launch. Setup.xcu: <?xml version="1.0" encoding="UTF-8"?> <oor:component-data xmlns:oor="http://openoffice.org/2001/registry" xmlns:xs="http://www.w3.org/2001/XMLSchema" oor:name="Setup" oor:package="org.openoffice"> <node oor:name="L10N"> <prop oor:name="ooLocale" oor:type="xs:string"> <value>en-US</value> </prop> </node> <node oor:name="Office"> <prop oor:name="ooSetupInstCompleted" oor:type="xs:boolean"> <value>true</value> </prop> <prop oor:name="LicenseAcceptDate" oor:type="xs:string"> <value>2008-05-09T11:32:20</value> </prop> <prop oor:name="FirstStartWizardCompleted" oor:type="xs:boolean"> <value>true</value> </prop> <node oor:name="Factories"> <node oor:name="com.sun.star.text.TextDocument"> <prop oor:name="ooSetupFactoryWindowAttributes" oor:type="xs:string"> <value>331,62,952,702;1;0,0,0,0;</value> </prop> </node> </node> </node> </oor:component-data> and UserProfile.xcu: <?xml version="1.0" encoding="UTF-8"?> <oor:component-data xmlns:oor="http://openoffice.org/2001/registry" xmlns:xs="http://www.w3.org/2001/XMLSchema" oor:name="UserProfile" oor:package="org.openoffice"> <node oor:name="Data"> <prop oor:name="givenname" oor:type="xs:string"> <value>DESIRED_FIRSTNAME</value> </prop> <prop oor:name="initials" oor:type="xs:string"> <value>DESIRED_INITIALS</value> </prop> <prop oor:name="sn" oor:type="xs:string"> <value>DESIRED_LASTNAME</value> </prop> </node> </oor:component-data> Just change around the variables to your liking and it'll work. Obviously you can also change the date when it thinks you accepted the EULA. With these settings, OpenOffice will never attempt to register, either. This worked for me, hopefully it works for others!
-
I've been using this forum a whole lot while developing some installation discs for the network I help manage - it helps a lot! I now have a question of my own, however: I'm installing Open Office 2.4 using the following command start /wait msiexec /qr /norestart /i openofficeorg24.msi This installs perfectly and silently. However when I start Open Office for the first time, I have to accept the EULA and enter my name and all that good stuff. Does anyone know how to eliminate this from happening? Thanks a bunch for the help and of course let me know if there are any questions about what I'm doing!