|
|
|||||||
| 論壇說明 |
|
歡迎您來到『史萊姆論壇』 ^___^ 您目前正以訪客的身份瀏覽本論壇，訪客所擁有的權限將受到限制，您可以瀏覽本論壇大部份的版區與文章，但您將無法參與任何討論或是使用私人訊息與其他會員交流。若您希望擁有完整的使用權限，請註冊成為我們的一份子，註冊的程序十分簡單、快速，而且最重要的是－－註冊是完全免費的！ 請點擊這裡：『註冊成為我們的一份子！』 |
 |
|
|
主題工具 | 顯示模式 |
2004-04-25, 09:20 PM
|
#1 |
|
註冊會員
|
4個問題求助~
OS:Windows 2000 pro
1.每次開機剛進入桌面後都會出現這個對話框  2.每次重開機我的燒錄器(J:\ )就會消失 到裝置管理員裡按"更新隨插即用"才會跑出來 但每次重開又會消失 3.我只要按<開始>裡的搜尋...expolor.exe就會當掉.... 4.還有在98系統裡的說明及一些應用軟體字型會顯示成這樣  謝謝~ |
|
送花文章: 0,
|
|
2004-04-26, 01:46 PM
|
#8 (permalink) |
|
註冊會員
|
很抱歉我沒打清楚
第1.2.3.點是我電腦的問題 系統是win2000 pro sp4 這現像是我使用完Registry Medic後才出現的 之後我使用回復設定後...情況還是一樣... 呼~第1點剛剛己解決了 第2點詳細情況是我只要按<開始>裡的搜尋 就會跑出windows installe的對話框 寫著"準備安裝"然後接著expolor.exe就當掉.... 第4.點則是我灌Win98的電腦時 常出現的問題,只是沒有注意看...平常沒發現而己~ 非常感謝大大們的回應..  |
|
|
送花文章: 0,
|
|
2004-04-26, 05:51 PM
|
#11 (permalink) |
|
註冊會員
|
1. 你的驅動是最標準的 但是你有裝ELBY程式 卻未顯現在你驅動中有點奇怪 請先完全反安裝 ELBY程式 至ELBY DVD-ROM 不會出現在你的裝置中
2. 下面用 REEDIT 找到下面的登錄值 點進去 "UpperFilters" 與 "LowerFilters" 中的 全部的值刪除 （無法直接刪除這兩個值,這是硬體層的登錄值）其餘的不要動 離開 （這是XP的值 2000我不知道是否相同) ------------------------------------------------------------------ [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E965-E325-11CE-BFC1-08002BE10318}] "UpperFilters"= "LowerFilters"= ----------------------------------------------------------- 3. 重開機數次 如果正常 裝回 ELBY程式 再測試看看 |
|
|
送花文章: 0,
|
|
2004-04-27, 01:46 AM
|
#14 (permalink) |
|
註冊會員
|
感謝snoppy大大的回應
我是想請教有關babayu大大所貼的登錄值的用意是什麼? 如以下 ------------------------------------------------------------------ [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E965-E325-11CE-BFC1-08002BE10318}] "UpperFilters"= "LowerFilters"= ----------------------------------------------------------- 謝謝~ |
|
|
送花文章: 0,
|
|
2004-04-27, 06:59 AM
|
#15 (permalink) |
|
註冊會員
|
這篇文章是國外論壇有人整理出來的 如果BIOS開機時能看見燒錄機或是光碟機 進入2000/XP OS 卻看不見 這是驅動程式有問題 下面的你看看吧
這是我安裝Roxio軟體 發現燒錄機與光碟機不驅動 到各論壇找答案 也順利解決 沒有讓問題惡化下去 現在我燒錄與各軟體搭配得很好 Just an addition to clarify the problem (all this is relevant to 2000/XP). If your virtual or physical device does not appear in Explorer then first go to device manager and check that corresponding CDROM is present there and Windows is using correct drivers for it. Daemon Tools does not provide CDROM drivers - Windows uses its standard Microsoft drivers bundled with OS. There must be at least storprop.dll and cdrom.sys which are mandatory. There may be also redbook.sys and some other filter drivers installed by 3rd party applications. Daemon Tools is only creating virtual SCSI controller with raw CDROM devices on it - but CDROM itself is controlled by Windows, not Daemon. All above mentioned drivers are automatically installed by Windows when you add new virtual or physical devices (eg. external USB CDROM). In this sense virtual drive acts same way any all other CDROMs. In some cases Windows may fail to install drivers, eg. if its catalog database is corrupt or some bad filter driver is preventing it - then you may need to manually select standard driver for it. If you have all correct drivers installed but CDROM is still not present in Explorer then you should check any filter drivers. You may have severe problems if you have eg. Roxio filter drivers present that are part of Easy CD or Windows Media Player in 2000 - even without Daemon Tools. Open the HKLM\SYSTEM\CurrentControlSet\Control\Class\{4D36E965-E325-11CE-BFC1-08002BE10318} key which controls 'DVD/CD-ROM' class of devices and check 'UpperFilter' and 'LowerFilter' values. In case of Roxio you may have cdralw2k.sys and cdr4_2k.sys there (cd4_xp.sys in XP). You may have system hangs or BSODs with these drivers in many situations: eg when new devices are added to system (virtual or USB) or some burning application or protected game is run. You may try to remove unwanted drivers by editing registry - be careful not to touch any other filter driver if any. These registry values are in fact REG_MULTI_SZ strings. After editing you will need to reboot then you can also delete these files from Windows\System32\Drivers folder. Do NOT just delete these files without correcting registry first - your CDROMs will not work at all then! You may have also other filter drivers. Drivers that are known NOT to cause any problems are ElbyCDFL.sys (from Elby or Slysoft) and PFC.SYS (from Padus), so it is unlikely you will need to remove them. Sometimes the problem is also caused by packet writing software which has bugs and does not handle correctly the dynamical addition/removal of devices in system. In this case you may try to uninstall/reinstall such software. All above problems are not related to Daemon Tools directly and may happen even with any other PnP device that is added to system on the fly - Windows is complex system and all components must obey certain rules. If some drivers behave bad - system stability is compromised no matter how good other drivers are. http://support.microsoft.com/default...b;en-us;320553 Revision history: 2003-03-16 Additions to S7 (help), S11 (MusicMatch), S18 (debug) 2003-03-02 Minor addition to section S17 (ADS utils) 2003-03-01 Minor revision of section S11 (registry removals) 2003-02-26 Major revision of section S17 (alternate data streams) 2003-02-22 Major revision 2002-12-11 Initial version ----------------------------------------------------------------- Although I'm not running W2K (98SE and XP Pro only), I've compiled a guide on troubleshooting InCD problems under W2K, based on input from other users. This guide (given below) may help some users until Ahead updates their FAQs and Help files (hopefully soon). In most cases recent versions of InCD should work if you use media matched to your burner with recent firmware, and your OS is reasonably clean (without drivers installed by other burning programs that conflict with InCD). Thus, before blaming InCD itself, you should test other factors carefully, and this may take a long time. If you want help from other forum members, follow the steps below and report as many details as possible. A bad (but frequent) example is where a user reports InCD problems after testing a single disc supplied with a new burner. Beware that packet writing with InCD is in general less reliable than multisession writing to CD-R discs with Nero. However, I am not trying to scare you away from packet writing. I have been using it for about five years without loosing a single file. For me it is more convenient than multisession writing when just a couple of files change between backups. But its unreliability shouldn't be ignored: I would never delete any important file from my HDD after copying it to an InCD disc. I intend to update this guide periodically. Hence I'll welcome comments, suggestions and especially reports of success stories. However, please refrain from posting messages such as "It didn't work for me" here; if you need help, start or join another thread. Simply speaking, if several users wanted to troubleshoot their individual problems in the same thread, this would only result in total confusion. Finally, here is the guide itself. ---Steps for Troubleshooting InCD Problems under Windows 2000--- S1. Upgrade the firmware of your burner to the latest version from your vendor's or original manufacturer's website. Frequently new firmware will enable your burner to accept more media. S2. Check your vendor's website for recommended CD-RW media. Search the Web (Google) for reviews of your burner and users' experiences with different media at www.cdfreaks.com , www.cdrinfo.com and www.cdrlabs.com . You may expect problems: 24x re-writers are fairly new and probably not tested much on older media, whereas 24x and even 16x media are hardly available. In particular, Memorex CD-RW discs are not recommended. S3. To check if your problems are not due to one specific brand of media, try several brands. Thus, depending on your burner, get at least a couple of 4x, 4x-10x, 4x-12x or 24x CD-RW discs from several better known vendors (see S2 above). Note that old 4x re-writers usually won't work with High Speed or Ultra Speed media. Unfortunately InCD no longer allows you to control rewriting speeds. In particular, if your burner is old, most probably it can't handle High Speed discs, which have "High Speed" included in the Compact Disc ReWritable logo on their covers, and are usually rated at 4x-10x or 4x-12x (but even 1x-10x indicates an HS disc, since the rated speed exceeds 4x). If your burner can only rewrite at 4x, its laser system doesn't meet the requirements of the newer HS technology. Then you should look for CD-RW discs rated at 1x-4x, or older discs rated at 2x. Such discs are gradually disappearing from the market, so in the long run, upgrading your burner may be the only solution. You can check which speeds are listed for your media in Nero itself (for a blank CD-RW), and in Nero CD Speed and InfoTool. BTW, the latest version of Nero usually installs quite recent versions of CD Speed and InfoTool (see Start | Programs | Ahead Nero | Nero Toolkit), which are highly useful for troubleshooting InCD; the latest versions may be downloaded from www.cdspeed2000.com . S4. If you wish to re-use a disc (e.g., because it failed in your experiments, or was formatted by earlier versions of InCD, DirectCD, etc), don't try to save time by using any quick formatting or quick erase options; always do full-erase in Nero | Recorder | EraseReWritable. Note that each CD-RW disc can handle only a finite number of rewrites. Manufactures may claim 1000 or more, but most users say 100 is a more realistic estimate. Yet there are tests showing that some poor media may become unusable after just 5 rewrites. To check your discs, you may run Nero CD Speed | Extra | CD Quality and Scandisc. S5. If InCD fails to mount a formatted disc, run CD Speed Scandisc to see if there are bad sectors, especially initial ones. S6. Before upgrading to the latest version of InCD from www.ahead.de , remove the previous version via Control Panel | Add or Remove Programs, selecting "Ahead InCD", and reboot. Similarly, remove "InCD EasyWrite Reader" and "InCD UDF Reader" if they are listed, and reboot. Since recent versions of InCD uninstall cleanly, there is little danger in version switching. Note, however, that InCD 3.37 has the infamous rename bug, and InCD sometimes fails to handle discs formatted with earlier versions (mostly CD-MRW discs, so back them up). To check if your burner is supported by InCD, see http://www.ahead.de/en/index.html#c1002822556070 http://www.ahead.de/en/index.html#recorder (you may choose Products | InCD | Supported Recorders if these links don't work). Since Ahead's documentation may be outdated, even if your burner is not listed, but it works with Nero, it will probably work with InCD as well. S7. Download the InCD manual from Ahead's site (Products | InCD | Documentation); although outdated, it gives general ideas about InCD. (In particular, the final format OK message has disappeared in recent versions, which give only the InCD mounted message.) The help in InCD versions downloaded from Ahead's site frequently doesn't work, because the setup program fails to put the help file InCD_US.chm into the InCD directory C:\Program Files\Ahead\InCD. There are three ways to get InCD_US.chm: S7.1. If you have a fairly recent Nero installation disc, you may find it on the CD (e.g., in the directory \Nero\InCD). S7.2. Run the InCD installation program (e.g., InCD35220b.exe) until it asks you: Reboot | Finish? At this stage, open Windows Explorer and navigate to your TEMP directory; on my box this is C:\Documents and Settings\KCK\Local Settings\Temp Its subdirectory RarSFx0 should contain InCD_US.chm; copy this file to C:\Program Files\Ahead\InCD before giving a final click to the InCD setup program (which will remove RarSFx0). S7.3. You may create a scratch directory C:\InCD and unpack the InCD installation program (e.g., InCD35220b.exe) to C:\InCD via, e.g., WinRar from www.rarlab.com or Total Commander from www.ghisler.com (using Files | Unpack Specific Files...); then look in C:\InCD. S7.4. To get some (again outdated) info, use Windows Explorer to call up C:\Program Files\Ahead\InCD\InCD.hlp and click Index, or anything else that's clickable (doesn't work in normal way). S8. Before formatting with InCD, make sure there are no "heavy" programs running in the background. Also before writing to InCD formatted discs, it may be wise to disable virus scanners, etc. There are differences between standard CD-RW (UDF 1.50) and CD-MRW (Mt. Rainier) formatting. (To verify whether your burner supports CD-MRW, see if Nero InfoTool | Drive has a checkmark for Mount Rainier, or right-click on the InCD icon and select InCD Property Sheet | InCD Page Settings to see whether the option "Format disc to CD-MRW" exists.) For instance, on a CD-RW 80min/700MB 10x disc, for a standard CD-RW (non-MRW) formatting, physical format takes about 8 min and logical format takes about 3 min (i.e., 11 min in total). In contrast, initial CD-MRW formatting takes about 30 sec (the disc is usable at this stage), whereas background formatting takes about 9 min (without influencing copy speeds); in both stages, ejecting the disc takes several seconds (this is for Lite-On LTR48125W). As for space, InCD reports 50KB used, 572MB free for CD-RW, whereas CD-MRW has 539MB free. Concerning readability of InCD discs in CD-ROM or DVD-ROM drives, XP with SP1 can read standard UDF 1.50 discs natively, whereas both standard and CD-MRW discs are readable under 98x, W2K and XP after installing Ahead's EasyWriteReader (download the latest version by selecting InCD | Utilities). This is independent of whether InCD is installed, but the reader should be MultiRead compliant (as are most drives used nowadays). Here is how you may format a CD-RW disc in InCD. A. Choose the standard CD-RW format or the CD-MRW (Mt. Rainier) format. Right-click the InCD icon in the taskbar notification area near the clock, and select Properties. When the InCD Property Sheet pops up, select InCD Page Settings, and either check or uncheck the option "Format disc to CD-MRW" (if this option is missing, either your burner doesn't support CD-MRW, or InCD isn't installed properly). I leave the other two options (messages and Safe mode) unchecked. Close the sheet. Alternatively, to call up the InCD Property Sheet, right-click your burner's icon in My Computer or Windows Explorer. B. Insert a blank CD-RW disc into your writer. When the InCD Disc Information pops up, you may cancel it (nothing useful there). Right-click the taskbar InCD icon and select Format. When the InCD Wizard starts running, press Next, then select a drive if you have more than one, and click Next. If you wish to change the formatting options, click on Properties to access InCD Page Settings; otherwise click Next. Choose the Volume Label (no spaces!) and click Finish. Formatting proceeds in two stages, and displays progress information (which is not always consistent). Finally, you'll see the InCD message "The disc was mounted in InCD UDF file format", as indicated by the green N-W arrow on the InCD icon. Note that some earlier versions of InCD eject a disc after formatting. The InCD icon should stay green while the disc is used (for copying, etc). When the disc is ejected, the InCD icon has a red S-E arrow (indicating there is no medium or InCD-formatted medium in the drive). As for using a previously formatted disc, on my box with Autorun on, after the disc is inserted, the arrow on the InCD icon flips from red S-E to green N-W after about 20 seconds, the InCD mounted message pops up, and Explorer shows the disc contents, unless I keep pressing the Shift key after closing the tray. The third possibility is that the icon is a yellow circle with an exclamation mark and a red S-E arrow, which means that no InCD-supported CD-RW drive could be found. (This may occur if an external drive is not turned on.) Finally, a big WARNING: Always Eject from the InCD icon or Explorer; using the recorder's eject button may spoil the disc! Ejecting via the button may seem to work, but if InCD doesn't finish properly, data will be lost (possibly later because some structural information is corrupted). BTW, if you want to keep an InCD disc in your drive for a longer period, you should first eject it after doing backups so that a proper TOC gets written; otherwise you could loose data if your system crashes! S9. If your burner supports CD-MRW (Mt. Rainier) formatting, experiment with it separately from the standard CD-RW (UDF 1.50) formatting. It may happen that your combination of burner/media/software will work only with one of these formats. S10. Sometimes InCD works only with Autorun off (as reported by Nero InfoTool | Configuration). To get Autorun off, either use Notepad to create a file called autorun0.reg that contains the following four lines REGEDIT4 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Cdrom] "AutoRun"=dword:00000000 and run it by double clicking on autorun0.reg in Explorer, or edit the registry. (If you replace the final 0 by 1, you'll get Autorun on.) The "proper" setting of Autorun for InCD may depend on the burner, its firmware, IDE bus, etc. Until Ahead clarifies this issue, one has to experiment. S11. Expect trouble if, before installing InCD, you ran other packet writers (e.g., Roxio's DirectCD), UDF readers (again Roxio's UDF Reader) or burning plugins installed "silently" by other programs (e.g., Windows Media Player, WinAmp, RealPlayer, etc). Such applications typically install drivers conflicting with InCD, which are not removed even if you remove the application itself. Still you should first try to remove such applications or their burning plugins via Control Panel | Add or Remove Programs before doing manual cleanups described below. S11.1. Since I've never installed such software, I can't identify all possible culprits, but you should look for files named as Cd*.sys, Cd*.dll, Ud*.sys, Ud*.dll. Here are listings from a user running W2K SP3: dir C:\WinNT\System32\Drivers\cd*.* 07/26/2000 19,080 cdaudio.sys 07/22/2002 61,104 cdfs.sys 07/22/2002 27,952 cdrom.sys dir C:\WinNT\System32\Drivers\ud*.* 07/22/2002 62,672 udfs.sys dir C:\WinNT\System32\cd*.* 08/29/2002 142,336 cdfview.dll 09/18/2001 118,872 cdm.dll 10/03/1998 703,760 cdo.dll 07/22/2002 402,704 cdont.dll 07/22/2002 2,524,944 cdosys.dll 07/26/2000 337,680 cdplayer.exe dir C:\WinNT\System32\ud*.* No Files whereas another user has in C:\WinNT\System32\Drivers an earlier version of cdaudio.sys (dated 12/07/1999), and in C:\WinNT\System32 only cdfview.dll 139 KB 8/29/2002 6:14 AM cdm.dll 110 KB 7/22/2002 2:05 PM cdonts.dll 394 KB 7/22/2002 2:05 PM For comparable listings, run these dir commands in a cmd (Command Prompt) window (opened via Start | Run | cmd). For instance, type dir C:\WinNT\system32\drivers\cd*.* >C:\dir1.txt and Enter to get the first listing in the file C:\dir1.txt. If you see other .sys or .dll files on your box, you may try renaming their .sys extensions to .sy_ and .dll to .dl_; however, before rebooting, you may also need to remove the registry settings for these files (see S11.5 below, especially UpperFilters and LowerFilters). S11.2. IMPORTANT: Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs; see the Microsoft Knowledge Base article 256986 "Description of the Microsoft Windows Registry": http://support.microsoft.com/default...b;EN-US;256986 S11.3. For example, after incomplete removals of Roxio's Easy CD Creator, DirectCD, UDF Reader or the Adaptec/Roxio burning plugin of Windows Media Player (WMP) 7.0, 7.1 or 9.0, you may still have the following files in C:\WinNT\System32\Drivers: Cdr4_2k.sys, Cdr4vsd.sys, Cdralw2k.sys, Cdudf.sys, Dvd_2k.sys, Mmc_2k.sys, Prtseqrd.sys, Pwd_2k.sys, UdfReadr.sys and in C:\WinNT\System32: Cdr4dll.dll, Cdral.dll, Cdrtc.dll After renaming these files (.sys to .sy_, .dll to .dl_), to clean the registry, either use Notepad to create a file called cdclean.reg that contains the following eleven lines REGEDIT4 [-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Cdr4_2k] [-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Cdr4vsd] [-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Cdralw2k] [-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Cdudf] [-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dvd_2k] [-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Mmc_2k] [-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Prtseqrd] [-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Pwd_2k] [-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\UdfReadr] and run it by double clicking on cdclean.reg in Explorer, or edit the registry, or use RegCleaner from http://www.vtoy.fi/jv16/shtml/regcleaner.shtml S11.4. For other (better) ways of removing the Adaptec plugin, and preventing it from being (re)installed by WMP, see http://www.nwlink.com/~zachd/pss/pss.html http://www.cdrlabs.com/phpBB/viewtopic.php?t=7494 In particular, to uninstall the Adaptec plugin of WMP 7.x, run rundll32 advpack.dll,LaunchINFSection %windir%\inf\adaptec.inf,Uninstall whereas for WMP 9.x you may run rundll32 advpack.dll,LaunchINFSection %windir%\inf\roxio.inf,Uninstall If you want to block WMP 7.1 or later from ever installing the Adaptec/Roxio plugin, you should run the adaptecblock.reg file, which contains the following four lines REGEDIT4 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MediaPlayer\Setup] "AdaptecBlock"="1" This will either create the AdaptecBlock keyword in the registry if it is missing (e.g., after a clean Windows installation), or change its value to 1 if it is already there. Concerning WMP 9.0, the MS information in http://www.microsoft.com/windows/win...er/readme.aspx says that Roxio CD Burning is available under W2K, and WMP can be removed via Add/Remove Programs, but it doesn't mention unistalling the burning plugin alone. S11.5. Incomplete removals of Adaptec/Roxio software may lead to startup problems (e.g., due to wrong UpperFilters or LowerFilters) and other issues discussed in the following MS Knowledge Board articles: 165863 Troubleshooting "Stop 0x0A" Messages in Windows 2000 and Windows NT http://support.microsoft.com/default...;en-us;165863& 269605 Windows Media Player 7 File List for Build 7.00.00.1954 http://support.microsoft.com/default...;en-us;269605& 270008 Cannot Access CD-ROM and "Code 31" Error Message in Device Manager After You Remove Adaptec Easy CD Creator from Your Computer http://support.microsoft.com/default...b;EN-US;270008 271268 Problems Running Windows Media Player 7 and CD Kakumei Virtual or Microtest Virtual CD http://support.microsoft.com/default...;en-us;271268& 314060 CD-ROM Access Is Missing and Messages Cite Error Code 31, Code 32, Code 19, or Code 39 After You Remove Easy CD Creator in Windows XP http://support.microsoft.com/default...b;en-us;314060 315345 "CD Recording Software Will Cause Windows to Become Unstable" Error Message When You Start Windows http://support.microsoft.com/default...;en-us;315345& In particular, to clean up UpperFilters and LowerFilters, either use Notepad to create a file called ulfilter.reg that contains the following five lines (note the possible wrap in line 3) REGEDIT4 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E965-E325-11CE-BFC1-08002BE10318}] "UpperFilters"=- "LowerFilters"=- and run it by double clicking on ulfilter.reg in Explorer, or edit the registry. Note that after the UpperFilters and/or LowerFilters values are removed, in general you may need to reinstall your burning software. On my XP Pro SP1 box, LowerFilters has the value bsstor, corresponding to the driver bsstor.sys installed by InCD 3.52.00b, whereas UpperFilters has the value incdrm, corresponding to the driver incdrm.sys installed by EasyWriteReader. To check your filters, open Registry Editor (Start | Run | regedit) and use Edit | Find... to search for "lowerfilters" (without the quotes); LowerFilters and UpperFilters are displayed in the right pane. For more information on upper/lower class filters, see http://www.bustrace.com/products/devfilter.htm S11.6. You may also ask Ahead's tech support for Nero CleanTool http://www.cdrlabs.com/phpBB/viewtop...?p=43897#43897 which may obviate the need for manual removal of conflicting drivers. S11.7. Here is some brief info on other burning plugins. Apparently no version of WinAmp installs any burning plugins by default, so typically users download them and install separately. The most popular ones include the Veritas CD Recording Plug-in, QuickBurn MP3, and Burning CD plugin, but there are many others which might conflict with Nero/InCD. RealPlayer is now called RealOne Player. For the free RealOne Player v1, one can buy Roxio CD Creator Plus, whereas in the commercial version of RealOne Player v2, CD burning is automatically available if you are a RealOne SuperPass member or a RealOne Player Plus user. You may expect conflicts with Nero/InCD, since Roxio CD Creator Plus is not compatible with RealOne Player v2. MusicMatch JukeBox may conflict with InCD, but usually it uninstalls cleanly via Add or Remove Programs; otherwise, you may need to rename its driver MxlW2k.sys in C:\WinNT\System32\Drivers and remove MxlW2k from UpperFilters; see S11.5. According to a user's report, MusicMatch 7.50.1070 may work with InCD 3.52.00b on XP SP1. S11.8. There may be conflicts between InCD and drivers for some storage devices, such as older models of Iomega Zip drives, in which case you should uninstall such drivers. S12. Check what Nero InfoTool says about your ASPI layers (both System and Nero). Nero and InCD don't need special ASPI; thus on my box, System ASP is not installed, whereas Nero ASPI WNASPI32.DLL 2.0.1.59 is installed and working properly. You may be in trouble if other burning programs required installation of special ASPI layers. Many users reported problems with the latest Adaptec's ASPI (4.7x), and frequently they had to to revert to version 4.6 by using ForceASPI from http://aspi.radified.com http://www.afterdawn.com/software/cd...ls/frcaspi.cfm S13. If your burner is connected to a RAID channel, try shifting it to an ordinary IDE channel. If your burner is connected through a USB Hub or extension cable, try connecting it directly to one of the USB ports on your computer. S14. Check if you have the latest BIOS and chipset drivers for your motherboard by visiting its manufacturer's site. Note, however, that sometimes the latest drivers may conflict with InCD. For instance, instead of using Nvidia IDE drivers, you may need to revert to the standard Windows drivers. Sometimes you may need to clean up ghosts for controllers (IDE, SCSI, USB, FireWire, Parallel Ports) and your burning devices in Device Manager (ghosts appear dimmer than installed devices). Some ghosts can't be seen even if you select "Show hidden devices" in Device Manager; a workaround is given in the MS KB article Q315539: http://support.microsoft.com/default...;en-us;Q315539 S15. If you are running Intel's Applications Accelerator, you may uninstall it temporarily to get a cleaner testing environment. Note that IAA may prevent Windows and Nero InfoTool from reporting correct information about your drives. S16. If your system freezes every few seconds, check if switching Autorun helps (see S10). Several users reported that their InCD slowdowns disappear when they leave a disc in their burner (so that InCD doesn't poll the burner to discover a fresh disc). Just remember not to leave an InCD disc in your drive, since it could be destroyed when Windows hangs and you have to power down your box. There are also reports about system freezes when InCD is used with certain network cards. This may not be due to InCD. For instance, users of some 3Com NICs frequently deactivate the option of "Software cable detect", because otherwise the NIC polling may cause system freezes every few seconds. S17. If you get errors while copying files from an NTFS volume to an InCD disc, inspect the error messages carefully. For instance, I used Explorer for copying a folder containing a hidden file Thumbs.db to an InCD CD-MRW disc (under XP Pro SP1). I got the dialog window: Confirm Stream Loss The file `Thumbs.db' has extra information attached to it that might be lost if you continue copying. The contents of the file will not be affected. Information that might be lost includes: Document Summary Info :encryptable:$DATA Do you want to proceed anyway? [Yes | No] to which I replied No; the copy finished as expected, i.e., all the files except Thumbs.db were copied. But when I replied Yes in another run, Explorer was "Not Responding", and I had to power off. BTW, nobody needs copies of Thumbs.db, but inexperienced users are likely to reply Yes to such copy querries. In contrast to Explorer, Total Commander (formerly known as Windows Commander) from www.ghisler.com copied Thumbs.db successfully. Hence if you get errors while copying other files, consider using Total Commander. Such errors may arise when some applications (e.g., virus scanners or archivers) add data streams to files on NTFS volumes. If anybody is wondering about "Confirm Stream Loss", take a look at Microsoft Windows XP Professional Resource Kit Documentation, Ch 13 File Systems, NTFS File System, Features Available on NTFS Volumes, Multiple Data Streams, Fig. 13.15, also available at http://www.microsoft.com/technet/tre...asp?frame=true More information on how to detect and remove alternate data streams is given in: http://www.sans.org/rr/threats/win_NTFS.php http://patriot.net/~carvdawg/docs/dark_side.html http://www.heysoft.de/nt/ntfs-ads.htm http://is-it-true.org/nt/atips/atips226.shtml http://www.sklobovsky.com/community/hidden2000/ http://www.ciac.org/ciac/bulletins/m-034.shtml http://www.cknow.com/vtutor/vtntfsads.htm http://www.diamondcs.com.au/streams/streams.htm In particular, I have tested two utilities for listing alternate data streams and their sizes: Streams v1.3 from Sysinternals http://www.sysinternals.com/ntw2k/source/misc.shtml and LADS v3.10 from Frank Heyne Software http://www.heysoft.de/Frames/f_sw_la_en.htm Their capabilities are similar, except that LADS's switch /XADSname allows to exclude ADS's with name ADSname (useful if your antivirus software creates ADSname streams). S18. If none of the preceding fixes work, you may ask for help by starting a new thread. Please provide as much information as possible, since frequently details that look irrelevant at first sight turn out to be crucial for diagnosing a problem. Of course, you should describe precisely your problem and the error messages you get from InCD and Windows (if any) and whether your problem arose after any recent changes to hardware or software. You should list the troubleshooting steps performed so far, and their results; if some step was skipped, explain why (e.g., not applicable, or you didn't know how to execute it). Your post should also answer the following querries. (If you don't know how to handle a querry, mention it, so that other users may help.) Q1. The model and firmware version of your burner, and how it is connected (internal IDE channel, USB (1.1 or 2.0) or FireWire (IEEE 1394), external interface (PCI or PC Card) if any). If you also have a CD-ROM or DVD-ROM drive, specify its model. Q2. Hardware info for your box: motherboard and chipset for desktops, manufacturer and model for laptops. Q3. Version of Windows service packs installed, if any. Q4. Versions of Nero/InCD and other burning programs or plugins, and whether Nero works correctly with your CD-RW media (otherwise there is little point in dealing with InCD before other problems are fixed). Q5. Brands and quantity of CD-RW discs used; if re-used, were they fully erased before reformatting? Q6. Format version (UDF 1.50 or CD-MRW) and whether it proceeded as in Step S8. Q7. What does Nero InfoTool | Configuration say about Autorun for your burner? Are the symptoms for your problem the same for Autorun set to on and to off? Q8. What does Nero InfoTool say about ASPI (both System and Nero)? Q9. If other burning programs or plugins had been removed, was InCD reinstalled after the registry had been cleaned either manually or via programs such as RegCleaner? Q10. The results of the dir commands described in S11.1. Q11. A suitable extract from Nero InfoTool report (click the diskette button to save it to a file). To save space, you may give only the Driver Information section, skipping all Microsoft drivers and those nonrelated to CD burning (e.g., modem, scanner, etc.; if unsure about a driver, don't omit it). An example from my XP box follows: Driver Information ------------------ Driver : BsStor Description : B.H.A Storage Helper Driver (WindowsNT5.x) Version : 1.0.7 Company : B.H.A Co.,Ltd. Driver : BsUDF Description : UDF File System Driver (WindowsXP) Version : 3.5.22.0 Company : ahead software Driver : incdrm Description : remapper Version : 1.0.0.3 Company : Ahead Software AG Q12. Once Nero is run, the file NeroHistory.log in C:\Program Files\Ahead\Nero lists useful system information. Since this file can be rather long, you may concentrate on its last session. Thus you may extract the initial information section (which ends with "Wizard: Off or On") and the final "Existing drivers" section from the Nero log file and post it. |
|
|
送花文章: 0,
|
平板模式
