EBK Posted January 10, 2007 Posted January 10, 2007 Thanks in Advance, I've been using ImgBurn for some time now. I recently upgraded to 2.1 and now need to be logged in as an Administrator to use it. The application screen, under Destination says: No Devices Detected! The log says I need Admin privileges - and when I switch to an Administrator, everything works perfectly. There is one post dated 4Dec05 that says to use the ElbyCDIO setting in I/O but I'd really rather continue as is and not download yet another set of drivers. Can anyone make a suggestion? My log file is shown below. Thanks, EBK I 12:12:39 ImgBurn Version 2.1.0.0 started! I 12:12:39 Microsoft Windows XP Media Center Edition (5.1, Build 2600 : Service Pack 2) W 12:12:39 Drive D:\ (FAT32) does not support single files > 4 GB I 12:12:39 Initialising SPTI... I 12:12:39 Searching for SCSI / ATAPI devices... E 12:12:44 CreateFile Failed! - Device: '\\.\CdRom0' (E:) E 12:12:44 Reason: Access is denied. E 12:12:49 CreateFile Failed! - Device: '\\.\CdRom1' (F:) E 12:12:49 Reason: Access is denied. W 12:12:49 Errors were encountered when trying to access 2 drives. W 12:12:49 These drives will not be visible in the program. E 12:12:49 You need Administrative privileges to use SPTI. W 12:12:49 No devices detected!
LIGHTNING UK! Posted January 10, 2007 Posted January 10, 2007 If you just updated, you must have already been using some other I/O Interface. SPTI has always required Admin permissions, that's just the way it works under XP. There's a post in the FAQ that might help you overcome the SPTI issue via a little editing of computer policies - all totally harmless of course!
EBK Posted January 10, 2007 Author Posted January 10, 2007 You hit the nail on the head! I forgot that I had been using it on my Win2K system! Thanks. EBK If you just updated, you must have already been using some other I/O Interface. SPTI has always required Admin permissions, that's just the way it works under XP. There's a post in the FAQ that might help you overcome the SPTI issue via a little editing of computer policies - all totally harmless of course!
Recommended Posts