-
Posts
518 -
Joined
-
Last visited
Reputation
30 ExcellentAbout acrobson

Personal Information
-
Location
Tyne & Wear
-
Hi all, Yeah thanks for the input. Later in the day after posting the thread and checking out Panasonic's FAQ pages it is normal behavior. The department are now using an external card reader. It seems they wanted to consolidate all of their many 4-8gb SD cards onto one low cost easy to mange 32gig SDHC card and transfer all their images onto that (as well as being backed-up on the network of course.....) However they were sure they had done it using the camera before and then realised it was a previous camera/different model. So yes, the USB port on the camera is a read only USB port to prevent people inadvertently formatting/overwriting their SD card with all the images on in error etc etc. Cheers, AC
-
I'm looking at somesones laptop and digital camera (Lumix FZ-48) and When they are trying to transer files or folders to and from the SD card plugged into a Lumix FZ48 it is reporting that write-protection is enabled. This only occurs when transferring files using the USB cable between the PC/laptop and the digial camera. However it works fine when using a card reader, attached to a laptop or a external USB card reader. This occurs on Windows XP, Vista SP1 & 2 and a Windows 7 machines so apepars to be an issue with the camera as appose to the PC/laptop it is connecting to. It has been tried with 10 different SD cards of all capacity's, various manfactures both new and old and the 'write protection sliders/switches' on the side of the cards are set to the 'unlocked' position, however they have been tried in both the locked and unlocked state. The switch's do appear to be functioning correctly as when they are set to the locked state they do report as being set to 'write protected' no-matter how you try and copy files to/from them. Any ideas?
-
Article: Getting started with LastPass password management
acrobson replied to Dos_Box's topic in Legacy CMS Comments
Also, the LastPast Android app charges after a trial period too. Granted it does 'sync' all your accounts to each of your devices. Personally I prefer managing this myself.Just thought I'd mention it before people go and set up their LastPass account and passwords and find they can't access it on their Android platform after 14 days.Good to see Edugeek back though! -
Article: Getting started with LastPass password management
acrobson replied to Dos_Box's topic in Legacy CMS Comments
I've used KeePass and find it more re-assuring that my data is stored where I choose it to be by me and move it around manually. It too is available on most platforms like Lastpass.Everyone has there favorites though. That's IT for you! -
Users being logged off immediately after logging in
acrobson replied to acrobson's topic in Windows Server 2000/2003
When the users login, 'Loading Personal Settings' is displayed and then fails to get to 'Applying Personal Settings', the user is then returned to the CTRL-ALT-DEL screen. Cannot be 100% if it displays 'Logging Off' or not as it is that quick. I will double check that on Monday also. -
Users being logged off immediately after logging in
acrobson replied to acrobson's topic in Windows Server 2000/2003
Not too sure, I shall check on Monday when I'm back in the office. If nothing has changed, why would this suddenly occur? -
Users being logged off immediately after logging in
acrobson replied to acrobson's topic in Windows Server 2000/2003
Yeah, it's across the network. -
Users being logged off immediately after logging in
acrobson replied to acrobson's topic in Windows Server 2000/2003
Failed to replicate the issue to date, local users can logon fine, however, domain user with or without a profile/homedrive seem to be those affected. -
Users being logged off immediately after logging in
acrobson replied to acrobson's topic in Windows Server 2000/2003
This has been tried and failed to resolve the issue, it re-occured the next time a user logged on ( -
Users being logged off immediately after logging in
acrobson replied to acrobson's topic in Windows Server 2000/2003
The local AD profiles have been removed both through 'System Properities' > 'Advanced System Settings' > 'User Profiles' as well as by deleting the users profile folder in C:\documents and settings\ As for the event logs, there is nothing displayed within there that points to anything of use. Machines hhave been removed and re-added to AD to re-gain trust with the domain as well as a /force update being ran for the GPO. GPO's have been checked, however nothing has changed in recent months in line with this happening, as well as that, not all machines are affected at the same time, it is totally random, with some machines being affected 5-6 times in the same day and others 1-2 times every few weeks. -
I have a problem where I have users who, when logging into their PC's are being logged off immediately, before even reaching their desktop. This is only affecting users who have roaming profiles and not the local admin account etc and it is not every user of the PC which is affected at anyone time. The user with the problem on one PC can go to another PC which they may have used before and machines which they have never logged on to and the problem may or may not occur there. So far I have removed the local copy of their AD roaming profiles from the PC's affected at the time, however, in X time frame, ranging from hours to days to weeks, the problem re-occurs. Network AD profiles have also be recreated, I.E, brand new AD accounts and the problem still persists. This is occurring on Windows XP SP2 and 3 machines. All have up to date anti-virus and have all be scanned and are clean. Some are brand new OS installations both by hand and from a RAS image as well as older machines which haven't been rebuilt for a while. Has anyone else come across this? My suspicion is a dodgy WSUS update, however, for all the goggling I have done, there seems to be very little information out there about this and what there is, is asking the same question without resolution. Thanks,
-
I've been using a PXE server using 3Com Boot Services and the 3com TFT server for a while. Had a few issues along the way, but nothing that couldn't be learnt from. I'm trying to re-image a new laptop model which we have, a Dell Inspiron 15R, which uses the RTL8103T Realtek network driver, however this apparently isn't on my PXE server which I half inherited and is not recognised with the Universal driver I am using which up until now, has never let me down. The situation is - I can take an image from the laptop fine, however I am unable to re-deploy the image to the same model of laptop with the same NIC otherwise it times out at some point, this can be anything from 2% to 30% to even 98% when it got my hopes up! The image can be re-deployed to another PC/laptop fine with a known compatible NIC and other machines image to and from the PXE fine without issue. The problem is, I am unable to deploy the image once taken. At first, I didn't think it could be a driver issue, as the Uni driver connected to the Ghost session and allowed the image to be taken and it does the same when deploying, expect it times out. How can I add another driver to the TFTPBOOT folder on the PXE server in order to re-image the laptop using the correct RTL8103T Realtek network driver? Thanks,
-
This appears to shine some more light on the issue - Ed's System Admin Blog: Patch Tuesday January 11, 2011 causes BSOD on Windows 7
-
Yeah, could be the same updates. My first one was last Monday/Tuesday evening.
-
Has anyone had problems after installing 'critical' updates for Windows 7 x64 in the last week? I have had three systems all running Windows 7 Professional x64 that have died after updates have been installed. One PC lost all of it's shortcut locations for 90% of the programs installed on the PC, including Office and a laptop blue screened every time the 'Windows Key' and 'R' were pressed to activate the 'RUN' dialog box whenever the wireless adaptor was active. Anti virus scans were run and came back clean, the event logs all displayed errors regarding a driver failure, these errors appeared immediately after the event logs for the updates having been installed. All of this was immediately post update installation and as a result, have had to be re-imaged.
