I've had and continue to have problems with cdwriter recognition on my system. I've 
done some research, and have found that many people have had the same problem, and 
it mainly revolves around the driver afs2k.sys. One person on these message boards 
suggests that afs2k.sys is most likely isntalled with HP software (I've plenty of 
that on my system, all my printer's are HP), and the removal of this file will most 
likely resolve the cdwriter recognition issue with XP and burning apps such as Nero, 
etc.

Any suggestions as to the removal of this annoying little file would be much appreciated. 
I'd track down this file and remove it right now, however I don't want anything else 
to stop working along with the cdwriter. I don't want to create more problems than 
I already have until I've heard from someone who's fixed a similar problem by removing 
this annoying little file.

Thanks everyone.


Anthony

Tip: Run a free scan for common Windows errors ad

re: Removal of afs2k.sys Friday, August 8, 2003 at 11:37 pm Posted by Ricer46 (23823 messages posted) You are right that it's a common problem, although I don't believe that it is unique to HP's. The safe way to remove the file is to simply rename it: afs2k.sy_ The XP file protection system may fight you on that one. You may have to do it in safe mode. It would be better if you had FAT32 than ntfs, far less could go wrong. On Friday, August 8, 2003 at 9:55 pm, Anthony wrote: >I've had and continue to have problems with cdwriter recognition on my system. I've >done some research, and have found that many people have had the same problem, and >it mainly revolves around the driver afs2k.sys. One person on these message boards >suggests that afs2k.sys is most likely isntalled with HP software (I've plenty of >that on my system, all my printer's are HP), and the removal of this file will most >likely resolve the cdwriter recognition issue with XP and burning apps such as Nero, >etc. > >Any suggestions as to the removal of this annoying little file would be much appreciated. >I'd track down this file and remove it right now, however I don't want anything else >to stop working along with the cdwriter. I don't want to create more problems than >I already have until I've heard from someone who's fixed a similar problem by removing >this annoying little file. > >Thanks everyone. > > >Anthony [Reply or follow-up to this message] re: Removal of afs2k.sys Saturday, August 9, 2003 at 12:03 am Posted by Anthony (16 messages posted) Thank you Ricer, I'll give that a shot, see if it works. I am using FAT32 on the disk XP is installed to, perhaps it's a good thing I've not reformatted to NTFS. Thanks again, I'll post the results of the next step momentarily. Anthony On Friday, August 8, 2003 at 11:37 pm, Ricer46 wrote: >You are right that it's a common problem, although I don't believe that it is unique >to HP's. The safe way to remove the file is to simply rename it: afs2k.sy_ >The XP file protection system may fight you on that one. You may have to do it in >safe mode. It would be better if you had FAT32 than ntfs, far less could go wrong. > > [Reply or follow-up to this message] re: Removal of afs2k.sys Saturday, August 9, 2003 at 12:20 am Posted by Anthony (16 messages posted) Ahhh, this just keeps getting better by the minute ... By renaming the file (thanks Ricer, glad I didn't remove it) neither of my cdrom drives (including the rewriter) are recognized by windows. I've now got a little yellow and black asterisk next to the two cdrom drives, and this message in the details for each, "Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39) Click Troubleshoot to start the troubleshooter for this device." Hopefully, the problem may be easily solved by naming it back to it's original name. Perhaps if I replace afs2k.sys with a newer version of the file, that would maybe fix things. Any ideas anyone? On Friday, August 8, 2003 at 9:55 pm, Anthony wrote: >I've had and continue to have problems with cdwriter recognition on my system. I've >done some research, and have found that many people have had the same problem, and >it mainly revolves around the driver afs2k.sys. One person on these message boards >suggests that afs2k.sys is most likely isntalled with HP software (I've plenty of >that on my system, all my printer's are HP), and the removal of this file will most >likely resolve the cdwriter recognition issue with XP and burning apps such as Nero, >etc. > >Any suggestions as to the removal of this annoying little file would be much appreciated. >I'd track down this file and remove it right now, however I don't want anything else >to stop working along with the cdwriter. I don't want to create more problems than >I already have until I've heard from someone who's fixed a similar problem by removing >this annoying little file. > >Thanks everyone. > > >Anthony [Reply or follow-up to this message] re: Removal of afs2k.sys - solved? Saturday, August 9, 2003 at 12:53 am Posted by Anthony (16 messages posted) I went over some of my research earlier this evening, and came across a post on another forum where a fellow tried renaming the file and installing CloneCD. I tried that, as I had nothing to lose. I installed it, it gave me some errors because my cdrom drives were invisible to the system, I clicked through them and finished the installation. I rebooted the pc, and as this fellow said in his post, CloneCD recognized the file as being corrupt and asked if I wanted to remove it and the registry entry for it, and as the other fellow did, I clicked yes, and did another reboot. So far both drives are visible, Nero is recognizing my cdwriter again after uninstalling/reinstalling the driver. However, I suspect Nero will continue to do the same thing as before with time, however I've at least narrowed down the possabilities and excluded the afs2k.sys file. I can't say problem is solved, however I hope it is. Thanks for the help everyone. Anthony On Saturday, August 9, 2003 at 12:20 am, Anthony wrote: >Ahhh, this just keeps getting better by the minute ... By renaming the file (thanks >Ricer, glad I didn't remove it) neither of my cdrom drives (including the rewriter) >are recognized by windows. I've now got a little yellow and black asterisk next to >the two cdrom drives, and this message in the details for each, "Windows cannot load >the device driver for this hardware. The driver may be corrupted or missing. (Code >39) > >Click Troubleshoot to start the troubleshooter for this device." > >Hopefully, the problem may be easily solved by naming it back to it's original name. >Perhaps if I replace afs2k.sys with a newer version of the file, that would maybe >fix things. Any ideas anyone? > > [Reply or follow-up to this message] re: Removal of afs2k.sys Tuesday, March 23, 2004 at 8:08 pm Posted by okokokmusic (1 messages posted) yeah... renaming that file makes everything work perfectly! now it recognizes cds that cannot be recognized previously! yay~ [Reply or follow-up to this message] re: Removal of afs2k.sys Sunday, December 5, 2004 at 8:15 pm Posted by ssufian (2 messages posted) Dear Anthony and Ricer... Your suggestion of "the problem may be easily solved by naming it back to it's original name" has gave me idea to try out the "System Restore" utility that is available in the WinXP Professional (I'm not sure whether this utility is available in WinXP home version or not). By using the System Restore utility, I have rolled back the system to the previous checkpoint and it solved the problem. Now I can use my QSI DVD/CDRW SBW-161 again. Therefore, I would like to suggest whoever facing this same problem to try out using this "System Restore" utility first before pursuing to other methods which I found out quite confusing and hard to follow especially for the person which does not have high level technical knowledge like me. On Saturday, August 9, 2003 at 12:20 am, Anthony wrote: > >Ahhh, this just keeps getting better by the minute ... By renaming the file (thanks >Ricer, glad I didn't remove it) neither of my cdrom drives (including the rewriter) >are recognized by windows. I've now got a little yellow and black asterisk next to >the two cdrom drives, and this message in the details for each, "Windows cannot load >the device driver for this hardware. The driver may be corrupted or missing. (Code >39) > >Click Troubleshoot to start the troubleshooter for this device." > >Hopefully, the problem may be easily solved by naming it back to it's original name. >Perhaps if I replace afs2k.sys with a newer version of the file, that would maybe >fix things. Any ideas anyone? > > [Reply or follow-up to this message] re: Removal of afs2k.sys Tuesday, December 7, 2004 at 8:23 pm Posted by Anthony (49 messages posted) The afs2k.sys thing was an intriguing experience. Solved some probs once it was removed. CloneCD did clean up the mess what with removing it and what not, from what I remember, though that did not solve my cdrw recognition prob. A firmware update solved that. It's too bad I hadn't gotten the firmware update sooner. That would have prevented alot of frustration. lol On Sunday, December 5, 2004 at 8:15 pm, ssufian wrote: >Dear Anthony and Ricer... > > Your suggestion of "the problem may be easily solved by naming it back to it's original >name" has gave me idea to try out the "System Restore" utility that is available >in the WinXP Professional >(I'm not sure whether this utility is available in WinXP home version or not). > > By using the System Restore utility, I have rolled back the system to the previous >checkpoint and it solved the problem. > > Now I can use my QSI DVD/CDRW SBW-161 again. > > Therefore, I would like to suggest whoever facing this same problem to try out using >this "System Restore" utility first before pursuing to other methods which I found >out quite confusing and hard to follow especially for the person which does not have >high level technical knowledge like me. > > > [Reply or follow-up to this message] Tip: Use one of the [Reply or follow-up to this message] links above to add a message to this thread Search this forum Start a new thread on a different subject Report abuse of the forum Return to the Windows XP Discussion Forum