Close to fixing??

Help!! I got the dreaded IPod with x's on it's eyes! I followed the online instructions to try to fix it. Here is where I am stuck. Please help!!
IPod Mini 4GB about 2 years old, have ITunes 7.02
I charged it up for a couple hours, then I've forced IPod into disk mode. While in disc mode it says it is updating/don't disconnect. Also, the IPod won't show on my ITunes, it did once and I tried to restore the original settings, except I got a mesage saying other programs were running, but were not. I cannot get the IPod to totally reset. Am I missing something? Am I close to restoring it or am I screwed?? HELP!!!!

I am trying to change the drive letter that has been talked about, but when I get to the Computer management screen, it says Media device, unreadable... so I cannot click on it to change also..

Similar Messages

Launching LR4 after a restart gives the error message "Lightroom encountered an error reading from its preview cache and needs to close" no fix on re

launching LR4 after a restart gives the error message "Lightroom encountered an error reading from its preview cache and needs to close" no fix on restart

Delete your preview cache, it is a folder whose name ends with Previews.LRDATA

Close to fixing? HELP!!

Help!! I got the dreaded IPod with x's on it's eyes! I followed the online instructions to try to fix it. Here is where I am stuck. Please help!!
IPod Mini 4GB about 2 years old, have ITunes 7.02
I charged it up for a couple hours, then I've forced IPod into disk mode. While in disc mode it says it is updating/don't disconnect. Also, the IPod won't show on my ITunes, it did once and I tried to restore the original settings, except I got a mesage saying other programs were running, but were not. I cannot get the IPod to totally reset. Am I missing something? Am I close to restoring it or am I screwed?? HELP!!!!

I am trying to change the drive letter that has been talked about, but when I get to the Computer management screen, it says Media device, unreadable... so I cannot click on it to change also..

So close to fixing this problem with iMovie clip frame rate!

Hi! Please help!
I'm recording short videos in iMovie using the built-in camera on my Macbook Pro. I did this yesterday and again this morning without incident. Everything worked great. Then, this afternoon, I made another video - EXACTLY the same way I'd done the other ones - and yet, this time, the clip mysteriously recorded at 18fps instead of 30fps. As a result (I think) the audio is out of synch. I have detached the audio as some have suggested in other forums, but this has not fixed the problem.
QUESTION: How can I convert the clip from 18fps to 30fps?? Is this even possible?? I'd really like to avoid re-recording, if at all possible.
I am a novice. Please explain any solutions to me as though I am a child. Thank-you!

mattias.rylander wrote:
I meant to say it only (if I may generalize here) makes a difference when you edit. Don't try to edit 30 fps material in a timeline meant for 25 fps. Very few applications can accomplish this with a good end result.
Are you speaking about this particular change of frame rates or any?
Having transfered Super 8 film that was shot at 18 fps, I have little choice but to change the rate. So far everything seems to be working out fine. For 24 fps iMovie does a pull-down of 1 1 2; for 30, 2 2 1. I'm a little confused as to whether I should use 24 or 30 fps. I'll be asking about this in a new thread.
The easiest way to change a projects framerate is to edit the project xml file.
Right click on your iMovie project file and choose "Show package contents..." (or something similar)
Edit the "Project" file (no extension) using the free Textwrangler editor or a plist capable editor.
Find the node "frameRate" and update to 30.
Really? That's a cool trick! But it sounds like it could easily mess things up. Have you tried this and with what scenarios?
or easier just create a new project
HTH
Message was edited by: betaneptune. Changed "under" to "with" for better clarity.

EA2: Manage Database closes connection [fixed]

Hi,
On closing the Manage Database window, sqldev automatically closes the connection and all other opened windows on it!?
Please bug this,
K.
Oracle 10.2, XP SP2

From what I have seen, the closing of other windows is limited by the preferences - ie it doesn't close worksheets/reports if the "close all worksheets/reports on disconnect" preferences are not selected.

Ipad 4 not charging, or connecting to wifi unless close. Fix?

I have an Ipad 4 that had issues on 6.1.3 and when I updated to ios 7.0.2 I had more issues. On both ios versions I could not connect to my wifi unless I was really close to the router, and now that I updated to ios 7 the usb cable stopped charging, I can connect to itunes but my ipad is practically useless now that it doesn't charge

the ipad keeps claiming the cable is not certified

7.7 Close / Quit freeze problem FIX

iTunes 7.7 close freeze FIX
Ok Amigos, i found the fix for this problem, at least for Windows Vista and Windows XP, this problem is a conflict with NOD32 antivirus system.
To fix you need to EXCLUDE from IMON and AMON the whole itunes folder and the my music/itunes folder.
For detailed instructions follow:
http://www.eset.com/support/kb.php?option=com_kb&Itemid=29&page=articles&article id=760
This fixed the freeze on my end, now itunes closes without problems. Give it a try.
Cheers!
-Andrés

I had this problem on all our computers, and of course, they all use NOD32. The fix from the NOD32 website worked perfectly. Thanks for finding this. zillionet, you are my hero! Apple tech support was no help.

Lightroom CC error message - cannot open previews - program closes when hit ok

Suddenly after using Lightroom CC for several months, I cannot open it. I get an error message saying "Lightroom encountered an error when reading from preview cache" and has to close; will fix next time. Many times later, still cannot open it. Anyone else with this problem or how to fix it? Thanks.

I had exactly the same issue and fixed it almost instantly by following the suggestion to rename the previews.lrdata folder in my latest lightroom backup file. This is the same as deleting it. When you then open Lightroom, it will regenerate the missing previews quickly and you will be back in business. My problem was caused by an interruption in the backup process which corrupted the file. John W.

Essbase execution inside fixes

Hello,
I need some clarifications if possible :)
In the following calculation, when are the values calculated if the 3 macros run inside the same fixed members and each macro needs the results from te previous one calculated?
I ask to be sure that I don't need to close the fix for each macro individualy.A simple comparison: Example 1 vs 2 would clear me out. In example 2 will it pass 3 times over the same number of blocks?
Thank you
Example 1:
FIX(A,B,C)
FIX(D,E,F)
%Macro1()
%Macro2()
%Macro3()
ENDFIX
ENDFIX
Example 2:
FIX(A,B,C)
FIX(D,E,F)
%Macro1()
ENDFIX
ENDFIX
FIX(A,B,C)
FIX(D,E,F)
%Macro2()
%Macro3()
ENDFIX
ENDFIX
FIX(A,B,C)
FIX(D,E,F)
%Macro3()
ENDFIX
ENDFIX

Yes, in this case I tested.
The case I had troubles in the past was with accounts wich formula that were dependent on other members with prior involved
I remember something along these lines:
Account1 formula: X + Z;
Account2 formula: @PRIOR(Account1,1,Scenario1:Scenario5);
In the calculation script I had something like:
FIX(Scenario1:Scenario5)
Account1;
Account2;
ENDFIX
And in this case the first time I run the process, Account2 would have no values so I needed to fix scenarios multiple times to solve it.
Thank you for your clarification.

Msi kt3 ultra, msi gf4 4200 tvout problem

I have a msi gf4 4200 64mb card and i have a msi kt3 ultra aru and windows xp,
my problem is tv out is garbled in pal , ntsc is grey (iam in europe), the colours seem inverted blues are red, etc and theres a ghosting effect around moving images like in videos or around the cursor
Ive tried everything from default mem setting , to high performance , tried diferent driver sets , tried windows 2000, tried via chipset drivers, latest msi, nvidia gf drivers, pal b , g , i , 60hz, diferent resolutions, clone view, single output to tv, stretch view , nothing seems to fix it, the only thing that comes close to fixing it is using the tvtool http://tvtool.info/ with color fix correction activated, but the images isnt stable its got a weird strecthing, shimmering effect on the bottom half of the tv image
Iam sure that the problem is not tv or cable related because i tried a friends p4 (board msi sis 645dx) with the exact same model gf4 4200 (not my one) with my scart cable and tv set up and it worked fine.
Could it be a voltage problem? ive even tried upping agp and core voltage a bit to see if helps, and nothing

mhuizing,
nope havent tried a diferent tv , but it should work , i tested the connection with a friends computer
exact same gfx card model and it worked fine!
My old system leadtek gf3 ti200 , epox 8kha+ worked fine with this connection.
Iam using a scart cable to a video , then from the vid to the tv via antena cable
i upgraded and voila, i got some headaches for free :P !!!

CS-5 Crashes when Edit / copy are used for pasting a new selection

Good morning,
I have downloaded CS5-Extended onto my PC as an upgrade to elements premiere 8. I still have the entire elements suite on my PC and functioning. The PC is a new Dell 4 core with windows 7, six G of RAM, and lots of HD space.
CS-55 works fine but has one very serious problem that seems to be a regular (several tests produce the same result) occurrance.
Selecting "edit" then "copy" when a selection is completely ready for copy/paste to a new layer freezes the entire program. No controls will do anything to the program no matter how long or what buttons are pushed. The PC stil works however with other programs which surprises me (I'm very computer literate).
The only method that I can find to close and "fix" the problem with CS5 after a crash is to completely shut down the entire PC and force a shutdown at that time (to get the PC to log off and shut down).
The real difficulty now occurs on re-starting the PC. The system seems to completely fill RAM on a re-start which makes the entire PC slow and almost non-responsive. This took some experimenting to "figure out." Starting regular office programs (Word, excel, etc) takes very long, and I get an intermittent "program not responding" display during the program start.
When started, the program(s) are extremely sluggish, and mouse pointers are not linear movement but "bounce" from place to place on the screen.
I considered doing a system restore to place the system back to a state before CS5 installation, but did more experimenting before this (in order to preserve the downloaded trial version of CS5 before my (already purchased) box arrives in the mail.
When starting CS-5 (after a crash and restart), it takes over a minute to start and does not respond well at all once started. When trying to open the previous file then "closing all files" the system seems to "unlock" all RAM and places the entire PC back to normal function.
This is a continuous problem affecting my system and all stems from an "edit / copy" set of commands.
Please help with this one. This problem is obviously a serious one and cannot continue with my set up.
My e-mail address is [email protected].
Thanks for the help; any other information you need to help diagnose this situation for a repair.
regards,
Peter 1269

Chris,
Thanks for the fast response. In answer to your questions, I’m using the 64 bit version of the CS-5 software. I have not received any bad “news” or reports about “bad ram.” This from IOLO system mechanic 10, and windows performance itself.
Let me try task manager / performance both before any Photoshop use, and after a crash. I’ll also get some information from system mechanic and any other sources that I can come up with.
I’m not sure why this crash happens after an “edit / paste” sequence and (possibly) not anything else. I just did however find the program crash under these circumstances:
Photoshop running with a (7mg picture loaded). Turn on elements organizer with a 35,000 picture catalog that I’ve been using in elements 7 and 8 (and premiere 8 ). Turn off organizer and return to Photoshop only to find that Photoshop is now frozen with a dual vertical arrow instead of a mouse pointer. No action will recover the program at this point.
Question:
Will my “preferences” in photoshop set to a very high ram allowance affect crashes in the program? What other preferences settings might be causing a problem.
I can talk to Dell tech support if need be as this PC is only 4 months old.
Thanks for ongoing help,
Peter1269

Is anybody else struggling with an intermittent connection when using the Magic Mouse/Trackpad ONLY on Boot Camp?

Hi,
I've seen thousands of posts about Bluetooth connection issues and interference and stutter/lag for both the Magic Mouse and Trackpad (affecting both Mac OS X and Windows under Boot Camp) but my problem is different.
To summarise my setup, I use:
- Retina MacBook Pro (lid closed or open, doesn't make a difference to this problem)
- Thunderbolt Display
- Wireless Keyboard
- Magic Trackpad (have also tried a Magic Mouse and experience similar issues to the Trackpad)
And in Mac OS X, everything works perfectly. The keyboard and trackpad work smoothly when I'm 6-7 metres from the machine, whether or not the laptop lid is open or closed, and whether or not the Thunderbold Display is connected.
But on to my problem: the bluetooth connection is incredibly unreliable/intermittent when in Windows (I run Windows 7 64-bit and Boot Camp 4.0, and got both devices connected without any trouble via Bluetooth).
But during usage, the cursor stutters/lags frequently, and tap to click (when enabled) seems to get triggered by mistake all the time (even when I'm not touching the Trackpad or even at the computer, clicks get registered).
The Wireless Keyboard is perfect, and works well 5 metres from the machine. The Mouse and Trackpad, though, don't even work reliably when they are 6 inches from the machine. The built-in trackpad on the laptop works perfectly too, in Windows and Mac.
I spent a week assuming I was suffering from Bluetooth interference, so I tried:
- using the laptop with the lid open
- removing the Thunderbolt display completely and trying the Magic Trackpad
- repositioning items on my desk
- disabling wifi
All of these adjustments made minor differences to how good/bad the Trackpad was, but none came close to fixing the problem or making it work as smoothly as under Mac OS X. It was only after doing all of this that I realised perhaps it was just a Apple driver for Windows issue, so I booted into Mac OS X and tested everything out, and sure enough, it's all perfect. But back into Windows, the Trackpad doesn't work reliably at all.
Obviously, the hardware is not at fault, and I assume the signal strength doesn't vary between operating system (why would it?) so I'm left believing this must be a driver issue. The TrackPad and Magic Mouse drivers have been out for a couple of years, so I'm surprised they can still be this bad. I tried both the latest driver from Boot Camp 4.0 (3.2.0.0) for the Trackpad, and also the older one from Boot Camp 3.2 (3.1.0.7) and both are equally bad for me.
So my question is: has anybody else struggled with using the Trackpad (or Magic Mouse) with Boot Camp 4.0 and Windows 7 64-bit, whilst finding it to be perfect under Mac OS? I haven't found many posts complaining about the Windows driver, which is why I assumed it was an interference issue. But I'm almost sure it isn't, having spent 2 weeks investigating.
Any thoughts/suggestions/answers much appreciated!
Kyle

SOLVED!
After much testing, I have found the cause of lagging/jumpiness on the Bluetooth Magic Mouse and Magic TrackPad in Boot Camp. Hopefully this will help others:
The drivers for the Broadcom 802.11n Wireless Adapter have a setting called "Bluetooth Collaboration" that is Disabled by default. Enabling this option removes the problem instantly. My Magic Trackpad now works flawlessly, even if I stand 6 metres from the machine. It now works just as well as under Mac OS. The setting can be found under:
Control Panel > Device Manager > Network Adapters > Broadcom 802.11n Network Adapter (right click and choose "Properties". Under the "Advanced" tab, highlight the setting named "Bluetooth Collaboration", then change it to Enable. Then click OK.
I narrowed the problem down to the wireless card by disabling ALL startup services and processes for Windows, then re-enabling one by one. As soon as I enabled the Windows Wireless Service, the problem came back. Similarly, disabling the Wireless Card inside the Network and Sharing Center (or Device Manager) removes the problem. This led me to believe it must be a driver issue with the wireless card, since the problem didn't occur with the Magic TrackPad under Mac OS, or on my mother's Windows 7 64-bit computer. So when I went into the Driver Properties to check for an update, I found this setting about Bluetooth Collaboration.
I really hope this helps others trying to use Bluetooth devices under Boot Camp. All Apple notebooks use the Broadcom card (and have done for years), so this driver is installed for almost anybody using Boot Camp on an Apple notebook. I'd assume this problem would affect anybody using Boot Camp + wifi + a Bluetooth device.
Cheers

Apparent kompare bug(s)

I apologise in advance for the length of this 1st-Arch-post-in-years. I value context more than brevity, I guess. Hopefully this is the longest post I'll throw at Arch for a long, long time.
I looked around (quite) a bit before filing this post. I've used Arch off-n-on since 0.4, know the Arch site, the basics about Arch, and most of the "gotcha's" farly well - but I'm no sysop, either.
I have a project I've been needing and meaning to work on for years (and which continues to compound itself while I don't); a huge set of backups on CD/DVD of all my data (my *life*, really) for well over a decade - letters, graphics, email, the first 40 pages of my book, you name it. Over the years this 'little' library has grown to over 10 GB compressed (30,000 files, *most* of them ARCHIVES). My guess is that 2-4 GB (compressed) of the data is important, some very much so.
My archive collection consists of many recursed archives themselves, and they're in about 8 or 10 different formats, to boot (even *.ice, LMAO). Many are further embedded several levels into the main archives (yes, I know that's a bad idea, but I didn't know that when I created them...). I BADLY need to unpack all this stuff, find and toss the duplicates, and truly organise (and efficiently backup) the remainder. This effort will obviously require a lot of automation (or else my heirs will either do it, or not).
I'd found a couple of useful tools in the Windows world years ago, but I don't buy software and the key piece of my suite was shareware that disabled itself after 30 days - not nearly enough time to plow through this boatload of bits.
A few months back I built a system with an Athlon XP 3500+ on an Asus A8N-E mobo w/512MB and 120 GB and 250 GB HD's. I'm hoping to go the RAID route soon - Linux software RAID, in fact. The 250 GB HD is running off an add-in PCI ATA card; both HD's have a UDMA channel all to themselves. The machine's got 4 extra fans, a nicely oversized 485W P/S, and the on-board sensors consistently show it running cool. I'm quite sure this isn't a H/W problem (I'm having no others; I built it myself...). This machine has been absolutely rock-solid in every other regard. I LOVE the system; now if I can simply use it for this one basically administrative project.
I finally have both the speed and the space required to tackle this now-monster project. When I "came home" to Arch a few months ago, I wanted to try several WMs/DMs; GNOME, KDE, E17, fluxbox and ratpoison (at least) are all loaded on my system, and I've booted most at least once. I'd assumed I'd have a LOT of options as to the tools to use.
I've been man-paging and googling and pacman -Q'ing (followed by more googling) for a couple of weeks through the course of my testing thus far, while trying various wrappers in various WMs. My concluson: Houston, we have a problem! <S>Maybe</S> Several.
In the past I've been partial to KDE (that's quickly changing), and it's what I started with this time around. As such, kompare seemed the obvious route to go, and had MOST (NOT all) of the functionality I needed (I also very much like it's GUI). Of course, kompare is simply a wrapper for diff (several diff variants, in fact, potentially). It's possible that diff is the problem. Hopefully further testing (and/or comments here) will make that determination more clearly.
Subsequent googling has revealed that the diff version shipped with Arch likely hasn't been completely functional at all levels in almost *5 YEARS* now. Diff's codefile timestamp is Sept. 3, *2002*! Version 2.8.1 (3.4 is current - just like *kompare*'s current version is 3.4). Additionally, directly below diff in that listing is diff3. Diff's codefile size is about 60K; diff3's is about 20K. *However*, they both have the same timestamp AND version # !!!
A *completely cosmetic* bug (http://bugs.kde.org/show_bug.cgi?id=138347) is fairly clearly the same bug as (https://bugs.launchpad.net/ubuntu/+source/kdesdk/+bug/45466 - 3-1/2 *YEARS* earlier!), and seemingly a trivial patch for a competent maintainer to create, at that. I've verified (w/o even trying) that this bug is resident in my system as we speak. Of course it is - the version of diff Arch is currently shipping was compiled almost a YEAR before the FIRST of the 2 bug reports above were filed! My Arch desktop O/S was installed less than a month ago using the 0.7.2 base ISO (kompare's timestamp is Jan. 20, 2007; version 3.4 - and it's a wrapper for a piece of code last compiled in 2002? What, the 2.0 kernel?). I've aggressively maintained my system current since my very recent install. See how well kompare/diff work on YOUR system...
Indeed, from the kompare bug page, it's hard to believe it's EVER been stable - or even used (see http://bugs.kde.org/simple_search.cgi?i … &offset=20 and just keep on clicking "View More Results" - or get yourself an energiser bunny to do it for you, maybe).
I copied the backups from CD's/DVD's to a clean, freshly-showered 64 GB (62.8, actually) ext3 partition (4K blocksize, defaults otherwise, journal included). I set up a top-level directory in this partition with 15 directories beneath it, one for each of my backup discs (whose contents range in size from 50 MB to 4.36 GB). I copied one archive to each directory, then unpacked them one at a time from the command line, removing the archive copy as I went. I ended up with about 15 GB of active data (25%).
I first configured kompare to use diff (w/no C/L options) running under KDE. As kdiff3 is kompare's preference, however, why is kdiff3 not already in the repos?
I'd not used it before, so I wasn't familiar with kompare's UI. I started out working with a few smaller subsets of the data I knew were near-perfect copies of each other and that wouldn't overload the filesystem. It seemed to act strangely; while I expected it to be well-optimised, both HD activity and CPU utilisation seemed extremely low for extended periods (and note my setup doesn't allow for a HDD LED for the HD on the controller card, where ALL the disk activity is going on).
After 3 runs in a row w/o a single errant file being found, I made a 2-byte mod to a small, non-critical text file that was part of the archive I was currently komparing, rebooting to make DAMNED sure cache was cleared, and reran kompare; identical results. The change STILL wasn't detected (the changed file still showed as being an exact copy of the original). The output I was getting was quite weird: usually, the 'kompare' would run at what seemed a rational speed; after a while a response screen would then open, *completely* devoid of data or messages. Immediately after that an odd dialogue box popped up; the title bar said "Error!", but the *message* was, basically, "No Duplicates Encountered." (or some such), or, more commonly, the same one I encountered repeatedly while searching the internet: "Could not parse diff output." (presumably because kompare still wasn't passing the proper parameters to diff). The program crashed about 1/2 the time (actually, give it a big enough block of data, and it'll crash every time). I was stunned 4 days later when ONE run (an exact duplicate of one I'd already attempted several times) resulted in "proper" output - *PERFECT*, with a complete and correct analysis - and completely unreproduceable, even after rebooting. It's ("It's" = proper analysis/output has) happened 3 times since, twice while working with data sets I would term 'trivial'.
So, in 2 weeks I got 3 runs w/o errors. I assure you I was trying at least 2 runs most days; a 1/2-dozen some days. By then, I also knew that kompare under KDE wasn't my only option - and I knew a bit more.
I use the "usual" repositories. When I finally checked diff's compile date, my jaw dropped: Sept. 3, *2002* !!! It's version 2.8.1; the current stable release is 3.4, and 3.5 is currently available for D/L (albeit not released). V. 2.8.1 works with the 2.6 kernel about as well as the original GWBasic compiler ('interpreter') does in WinXP...and may have been this way for a long time.
More research (difficult, given the age of what little kompare documentation is available on the web). The primary maintainer apparently got removed from maintaining the package in 2003 (and, I presume, other packages, as well) for what appeared to be 'apathy' (MY words). He 'forgot' to include an update after saying he would do so (a patch to pass the appropriate parameters to diff, hopefully fixing the "Could not parse diff output." message, and maybe even straighten out my anomolies, as well).
Kompare hasn't been updated since. Diff3 IS currently being maintained. Actually, even though diff3 has apparently replaced diff, *kompare* prefers kdiff3. For that matter, from my reading thus far, diff, diff3, vimdiff and cmp ALL may possibly be useable (the latter would require some scripting). Further, ALL the following may possibly be made able to work as wrappers (in decreasing order of likelihood, IMNSHO): kompare, krusader, meld, and emelFM2.
So, diff is broken, and it doesn't appear that it's going to be fixed...I personally was a bit consternated when I realised just how off-the-rails kompare was. I see a function such as that provided by kompare as both *critical* AND as a 'black box' function - it HAS to work. Just like the ALU MUST compute 2+2 = 4, or the 'computer' becomes a boat anchor...
So, I D/L'ed meld (for GNOME; it runs under KDE but no help is avalable), then emelFM2 (written for E17, I believe). I've spent the past week trying various combinations of (a) kompare, krusader, meld and emelFM2 as wrappers for diff under (b) KDE, GNOME, and E17. The results have been SO inconsistent it's scary. This includes both giving apparently proper results with a big job on rare occasion (but not consistently reproduceable), and VERY bizarrely, on one occasion, wiping a brand new, 64 *GB* ext3 partition CLEAN. I assure you the remainder of my testing will be on a dedicated partition! This HD is almost braad-new and has given me ZERO other trouble.
Meld was the most consistently performing diff setup I used (on any WM; it worked on them all).
I plan to spend the next 1-2 weeks doing some detailed and structured testing of all possible combos of wrapper/driver/WM, rather than just diff. I also plan to see if it's possible to pass command-line parameters to diff from kompare (if I have the time to spend ANY more w/kompare; kompare clearly isn't what I need - even though it had the . Yes, I *do* know how many combos of 4 wrappers, 4 drivers, and 3 WM's there are (48); my college major was statistics, LOL. And 48 test runs is adequate to test each combo, ONCE...
To me, this task is like big sort jobs were on mainframes a (human, not computer!) generation ago: potentially very large, critical tasks, the results of which aren't always easy to manually double-check. Surely many, if not most, users have a manner of doing this. Diff has apparently been broken for maybe 5 years and THAT wouldn't have gone unnoticed - am I one of the VERY few to even try to use kompare? What do the rest of you use?
Note that after locating and reading as much kompare documentation as possible (I read more BUG reports than anything), I made several important discoveries:
(a) kompare isn't really set up for binary files; it's intended for use with text files. You can specify an option to force a text-mode search, but you apparently canNOT do the reverse.
(b) It err'ed out comparing two M$ 'Word' files, stating they "were binary"...
(c) Worst of all, for me: These files have been archived to CD or DVD, usually repeatedly, and then copied back to disk (I've lost 3 good-sized archives this way - which does serve to somewhat justify my apparently obsessive need to backup files). Kompare does do individual file comparisons (ie, if you specify both files on the command line) byte-by-byte (block-by-block, whatever), but if you request that it compare *directories*, filename and size are all it considers (it appears from the sparse documentation I've seen that this is corrected in the *current* version, . The duplicate-file tool suite I used in Windows did an MD5 hash on *every* file, no matter the size; I *knew* when a bit error had creeped in, and usually knew fairly quickly. Not finding out you have a bad backup until it's the only copy of your data you have left is no good!
Anyone have any suggestions on doing this task efficiently and reliably in Arch?
Again, I believe this to be an upstream problem in a way, but my guess is that if we were using the *current* diffutils to match the KDE version (and a maintainer had done his job in a timely fashion) this bug would NOT exist. My advice, at least until Arch can get diff3 (or, preferably, kdiff3) packaged, STAY AWAY FROM kompare !!! At least with anything critical, at least until this issue is better understood.
Kompare (and diffutils, as well, IMO) needs to be removed from the 'public' repo's until it's close to fixed, at least. Just pkgbuild'ing the current diffutils version (or kdiff3!) is likely the easiest way out. Who knows, MAYBE I'll take a stab at that myself. No promises.
For ANYONE still reading, WOW! TIA. Really. Sorry for the tome.
Blue Skies...g
"It's a lot easier to throw grenades than it is to catch them!" -- Tim Russert

[intro, backups, bla...]I BADLY need to unpack all this stuff, find and toss the duplicates, and truly organise (and efficiently backup) the remainder.
Ok, that's what it's all about.
I'd found a couple of useful tools in the Windows world years ago, but I don't buy software and the key piece of my suite was shareware that disabled itself after 30 days - not nearly enough time to plow through this boatload of bits.
Total Commander rocks.
[killed half a dozen paragrahps or so] It's possible that diff is the problem.
Contratulations. You managed to post 3K of text but still failed to mention what the problem is.
Subsequent googling has revealed that the diff version shipped with Arch likely hasn't been completely functional at all levels in almost *5 YEARS* now. Diff's codefile timestamp is Sept. 3, *2002*! Version 2.8.1 (3.4 is current - just like *kompare*'s current version is 3.4).
http://www.archlinux.org/packages/search/?q=diffutils
You will notice that package isn't flagged out-of-date. That's because the (still current) upstream version is (tadaa!) 2.8.1. Please tell us where you found that 3.4 version.
Additionally, directly below diff in that listing is diff3. Diff's codefile size is about 60K; diff3's is about 20K. *However*, they both have the same timestamp AND version # !!!
WTF??? What listing? You know that diff and diff3 are different programs but still part of the same upstream sources, don't you?
[non-relevant nonsense...] See how well kompare/diff work on YOUR system...
They work fine.
[kompare bashing]
Take a look at the URL, bugs.kde.org, not bugs.archlinux.org. Got it?
I copied the backups from CD's/DVD's to a clean, freshly-showered 64 GB (62.8, actually) ext3 partition (4K blocksize, defaults otherwise, journal included). I set up a top-level directory in this partition with 15 directories beneath it, one for each of my backup discs (whose contents range in size from 50 MB to 4.36 GB). I copied one archive to each directory, then unpacked them one at a time from the command line, removing the archive copy as I went. I ended up with about 15 GB of active data (25%).
I think I could rest my case already at this point.
I first configured kompare to use diff (w/no C/L options) running under KDE. As kdiff3 is kompare's preference, however, why is kdiff3 not already in the repos?
It is: community/kdiff3 0.9.91-1
(I will skip some paragraphs about the actual kompare usage and come back to that at the very end.)
I use the "usual" repositories. When I finally checked diff's compile date, my jaw dropped: Sept. 3, *2002* !!! It's version 2.8.1; the current stable release is 3.4, and 3.5 is currently available for D/L (albeit not released). V. 2.8.1 works with the 2.6 kernel about as well as the original GWBasic compiler ('interpreter') does in WinXP...and may have been this way for a long time.
Please quit that bullshit and show us version 3.4 of the GNU diffutils.
Kompare hasn't been updated since. Diff3 IS currently being maintained. Actually, even though diff3 has apparently replaced diff, *kompare* prefers kdiff3. For that matter, from my reading thus far, diff, diff3, vimdiff and cmp ALL may possibly be useable (the latter would require some scripting). Further, ALL the following may possibly be made able to work as wrappers (in decreasing order of likelihood, IMNSHO): kompare, krusader, meld, and emelFM2.
Check http://websvn.kde.org/ to follow the development progress of kompare, it's part of kdesdk. diff3 is from diffutils 2.8.1 and I wouldn't call that "maintained", but you already know that. It is obviously not a replacement for diff, did you ever read the manpages? And wow, a KDE program prefers to use another KDE program!
[killed quite a bit]Diff has apparently been broken for maybe 5 years and THAT wouldn't have gone unnoticed - am I one of the VERY few to even try to use kompare? What do the rest of you use?
Again, diff is fine and I'm using kompare (or kdiff3?) almost daily, in krusader.
(a) kompare isn't really set up for binary files; it's intended for use with text files. You can specify an option to force a text-mode search, but you apparently canNOT do the reverse.
(b) It err'ed out comparing two M$ 'Word' files, stating they "were binary"...
Genius. Comparing binary files is useless. If you used MS Office you're hosed, that simple. More useful advice at the end.
Anyone have any suggestions on doing this task efficiently and reliably in Arch?
Yep.
Again, I believe this to be an upstream problem in a way, but my guess is that if we were using the *current* diffutils to match the KDE version (and a maintainer had done his job in a timely fashion) this bug would NOT exist. My advice, at least until Arch can get diff3 (or, preferably, kdiff3) packaged, STAY AWAY FROM kompare !!! At least with anything critical, at least until this issue is better understood.
Upstream, right... diffutils have nothing to do with KDE at all... Arch has diff3 and kdiff3 packaged ... it's no 'issue' at all.
Okay, I apologize for that 'tone' of mine but I get pissed easily when wasting so much time on something as this.
I know your problem very well as I'm constantly backing up stuff, comparing directories and hunting duplicates.
After unpacking everything the first step to take is to run a comprehensive check for binary duplicates. My tool of choice for that task is Total Commander (Win32 shareware, no timeout, just a minor nag screen on start, works fine with Wine). Just a few random keyboard shortcuts you might find handy (see the help file for explanations): ctrl-b, ctrl-f1(-f6), ctrl-c,y, alt-f7
After killing them, go on to compare ("synchronize") similar directories, either with Total Commander, Krusader, rsync, diff -R, whatever.
If you encounter similar named files, check the dates and kill the older ones, or compare them if they're not binary.
And so on... you know best what kind of data you got and how to split it up.
Throwing plain diff on a set of thousands of files, possibly gigabytes is a huge waste of time and computing/power resources. Adding a frontend will make it crash most of the time, especially with binary files. I think using kdiff3 to compare the Arch Linux 0.8 base beta1 iso to the beta2 one alone should suffice. A few more gigabytes of RAM might help though.

Unable to connect wifi via netctl - Unregistered Authentication Agent

I have a previous post int the Newbie Corner that went unanswered, so I figured I'd try again here now that I have some new information. The post is here...
https://bbs.archlinux.org/viewtopic.php?id=197031
And here's a copy of that post so you don't have to open it in a new tab.
ORIGINAL POST:
I have continually been having issues with netctl failing to start an automatic profile for awhile now, but I have been able to manually bring up my connection once my system is up and running. Today I am running into the issue where netctl will outright fail to connect during a manual attempt. When viewing journalctl -xe the error I receive is:
WPA association/authentication failed for interface 'wlan0'
Failed to bring the network up for profile
I noticed that there is a 'fix' for this issue on the Arch Wiki which simply states to bring wlan0 down with ip link, then to start the profile with netctl again. I went ahead and gave that fix a try and got a new error.
Unregistered Authentication Agent for unix-process:1324:44567
The error goes on to provide a path to .../PolicyKit1/AuthenticationAgent,.
I have tried using NetworkManager as well, but I'd prefer not to use it as I seem to have more problems with it over netctl, and that is why I currently have it disabled. Any advice on how to proceed would be appreciated. Also, I was connected to my home wifi last night without a problem, and I have tested the wifi connection with my phone, which authenticates and connects without a problem.
EDIT:
I did a bit more digging and found some startup errors issues via dmesg with wlan0.
IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: authenticate with 00:24:b2:71:b8:27
wlan0: direct probe to 00:24:b2:71:b8:27 (try 1/3)
wlan0: direct probe to 00:24:b2:71:b8:27 (try 2/3)
wlan0: direct probe to 00:24:b2:71:b8:27 (try 3/3)
wlan0: authentication with 00:24:b2:71:b8:27 timed out
The last 5 lines of this error repeats about 7 times before stopping. I use a broadcom card and my 43xx driver loads without a problem, I've been using it for awhile now on various distros.
b43-phy0: Broadcom 4311 WLAN found (core revision 10)
EDIT:
Well after doing some research, I found this existing bug.
https://bugs.archlinux.org/task/44821
Involving wifi not working under kernel 4.0.1. I noticed a Broadcom card listed by one of the users who was having the same problem, so at this point I'm probably going to wait until I get home to test my laptop on my home wifi again, then if I run into problems I'll downgrade my kernel and see how things go.
NEW POST:
So after all of that I tried my laptop at home again, and netctl-auto connected flawlessly to my wifi at home, which has led me to believe that the problem has to do with the message...
polkitd[1087]: Unregistered Authentication Agent for unix-process:2582:96758
I had previously noted that I would downgrade my kernel, but at this point I'd hate to do that considering netctl-auto is working.
I have also tried connecting via wifi-menu, and when I try that I get the message
Interface 'wlan0' is controlled by netctl-auto
After which authentication fails. I have stopped netctl-auto via systemctl using systemctl stop [email protected] and tried again. I end up receiving the message error message from systemctl that the job failed, and viewing journalctl -xe shows the recurring Unregistered Authentication Agent from polkitd.
Any help would be appreciated.
EDIT:
The issue continues. I have enabled the netctl profile I am currently working in netctl-auto with netctl enable profile, and that has not allowed the profile to automatically start up as it would with my home wireless connection. Something I have been noticing is that upon boot, without attempting to connect with netctl, is that wlan0 is not up.
IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
I have manually brought it up and immediately receive a failed message from systemd regarding my profile in netctl. If I do not manually bring it up with ip link set dev wlan0 up, then when I try to connect with netctl start profile, netctl will not bring wlan0 up and it will leave it in it's previous state.
The odd thing is, even with wlan0 in a down state, systemd is giving me the error message...
WPA association/authentication failed for interface 'wlan0'
Which is odd because netctl shouldn't be able to pass authentication is wlan0 is still down.
I've been at this for 2 days now and am no closer to fixing this than I was yesterday. I could really use some assistance. At this point I believe I may just downgrade my kernel and hope this fixes the issue, if not then I'm silently hoping my laptop won't connect to my home wifi when I get home so I can diagnose this problem via ethernet.
EDIT:
Well here's something new. When viewing why netctl-auto fails on startup via systemctl status [email protected] I am getting the reason of
Could not create the configuration file for interface wlan0
At least now I have a bit more to work with.
Last edited by barefly (2015-05-06 22:30:39)

Use this article: iOS: Wi-Fi settings grayed out or dim - Support - Apple
Follow all of the troubleshooting steps. You can even try restoring the device as new: iOS: How to back up your data and set up your device as a new device
If the wi-fi remains greyed out, your device needs service.
If within warranty, it should be free.
If not, it will probably cost $199 USD + tax.

Why does it take 10 to 15 minutes to get my start page open?

well i have set fire fox to open my start page, but after opening my fire fox browser, it takes any where from 10 15 and some 20 minutes to open my start page, and some times it will open after that time then open and close again then finally open. I have the latest fire fox, and already tried all suggested ideas in help none has even come close to fixing my problem. what is going on with fire fox. are they sleeping?

Hi starsh1,
"....15 and some 20 minutes to open my start page..." it's really a life time !
see in the next link a lot of causes that this can happen
[https://support.mozilla.org/en-US/kb/firefox-takes-long-time-start-up Firefox takes a long time to start up]
check specially : [https://support.mozilla.org/en-US/kb/troubleshoot-extensions-themes-to-fix-problems Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems]
thank you

Close to fixing??

Similar Messages

Maybe you are looking for