進階會員 | 引用:
| |
會員 | 請問一下,出現 "CDBOOT:Couldn't find NTLDR" 是什麼意思?? 是有哪個步驟有問題嗎?? 燒XP開機光碟我是知道怎麼燒,但是有選單的我就不了解了~~~ |
風中的羽翼 | 引用:
確定你已經用 16 進位程式編輯過 VOL1.DAT 或 VOL2.DAT 了(注意大小寫) SETUPLDR.BINBOOTFIX.BINI386 應該改成 SETUPLDR.BINBOOTFIX.BINVOL1 或是 VOL2 | |
進階會員 | 引用:
先前用nero的開機光碟模式(開機映象檔,我是用第一篇附的的xpboot.bin) 做出來的CD,也會出現"Couldn't find NTLDR" 我的解決方法是: 將上面lamina兄的多重開機部分做完後,用CDImage生成iso檔 再用nero燒出來 CDImage GUI設定法: 舉個例(gosh下的參數) 引用:
08/23/2001,09:00:00 <--檔案時間 l t b h n m o <--必須勾選的選項 c:\install\loader.bin <--開機映象檔的位置 XPSP1 <--光碟名稱 c:\install <--要燒錄的光碟檔案所在位置 c:\xpsp1.iso <--生成以xpsp1檔名的iso檔 ================================================================ 個人猜測,出現錯誤的關鍵是,開機光碟模式的開機映象檔,必須用 loader.bin而不是xpboot.bin ================================================================ CDIMAGE GUI version English Beta 3 http://www.tech-hints.com/prog/cdimagegui.zip | ||
風中的羽翼 | CDIMAGE 的參數...參考看看 Usage: CDIMAGE [options] sourceroot targetfile -l volume label, no spaces (e.g. -lMYLABEL) -t time stamp for all files and directories, no spaces, any delimiter (e.g. -t12/31/2000,15:01:00) -g encode GMT time for files rather than local time -h include hidden files and directories -n allow long filenames (longer than DOS 8.3 names) -nt allow long filenames, restricted to NT 3.51 compatibility (-nt and -d cannot be used together) -d don't force lowercase filenames to uppercase -c use ANSI filenames versus OEM filenames from source -j1 encode Joliet Unicode filenames AND generate DOS-compatible 8.3 filenames in the ISO-9660 name space (can be read by either Joliet systems or conventional ISO-9660 systems, but some of the filenames in the ISO-9660 name space might be changed to comply with DOS 8.3 and/or ISO-9660 naming restrictions) -j2 encode Joliet Unicode filenames without standard ISO-9660 names (requires a Joliet operating system to read files from the CD) When using the -j1 or -j2 options, the -n, -nt, and -d options do not apply and cannot be used. -js non-Joliet "readme.txt" file for images encoded with -j2 option (e.g. -jsc:\location\readme.txt). This file will be visible as the only file in the root directory of the disc on systems that do not support the Joliet format (Windows 3.1, NT 3.x, etc). -u1 encode "UDF-Bridge" media -u2 encode "UDF" file system without a mirror ISO-9660 file system (requires a UDF capable operating system to read the files) -ur non-UDF "readme.txt" file for images encoded with -u2 option (e.g. -usc:\location\readme.txt). This file will be visible as the only file in the root directory of the disc on systems that do not support the UDF format. -us sparse UDF files -ue embed file data in UDF extent entry -uf embed UDF FID entries -uv UDF Video Zone compatibility enforced -b "El Torito" boot sector file, no spaces (e.g. -bc:\location\cdboot.bin) -p Platform ID for the "El Torito" boot catalog -e Do not set floppy emulation mode in El Torito boot catalog -s sign image file with digital signature (no spaces, provide RPC server and endpoint name like -sServerName:EndPointName) -x compute and encode "AutoCRC" values in image -o optimize storage by encoding duplicate files only once -oc slower duplicate file detection using binary comparisons rather than MD5 hash values -oi ignore diamond compression timestamps when comparing files -os show duplicate files while creating image (-o options can be combined like -ocis) -w warning level followed by number (e.g. -w4) 1 report non-ISO or non-Joliet compliant filenames or depth 2 report non-DOS compliant filenames 3 report zero-length files 4 report each file name copied to image -y test option followed by number (e.g. -y1), used to generate non-standard variations of ISO-9660 for testing purposes: 1 encode trailing version number ';1' on filenames (7.5.1) 2 round directory sizes to multiples of 2K (6.8.1.3) 5 write \i386 directory files first, in reverse sort order 6 allow directory records to be exactly aligned at ends of sectors (ISO-9660 6.8.1.1 conformant but breaks MSCDEX) 7 warn about generated shortnames for 16-bit apps under NT 4.0 b blocksize 512 bytes rather than 2048 bytes d suppress warning for non-identical files with same initial 64K l UDF - long ads used in file entries instead of short ads r UDF - number of ad's is random w open source files with write sharing t load segment in hex for El Torito boot image (e.g. -yt7C0) f use a faster way to generate short names -k (keep) create image even if fail to open some of the source files -m ignore maximum image size of 681,984,000 bytes -a allocation summary shows file and directory sizes -q scan source files only, don't create an image file |
北海道的熊 | 引用:
關於HOTFIX的部分,弟是以Svcpack的方式製作,感覺上速度沒啥差異。 這兩種安裝的差異只有一種,以HOTFIX方式安裝的話,新增/移除程式看的到,無法移除。 如果是以GuiRunOnce去執行HOTFIX.CMD的方式安裝的話,新增/移除程式看的到,可以移除。 不過,以Svcpack安裝的話,會發生如foxbrian兄所說的,WMP9的問題 個人偏好採用Svcpack的方式安裝HOTFIX CMD檔弟已經改到麻痺了,隨時可以變動兩裝安裝方式而不混亂了 製作→燒錄→安裝→測試→修改 已不下30次的神經病 | |
進階會員 | 引用:
引用:
開始->執行->C:\QFECHECK.exe /l 程式就會產生已安裝hotfix的清單,無論怎麼整合的都無所遁形 PS.微軟怎麼老是出一些沒有GUI的工具啊 | ||
會員 | 引用:
| |
會員 | 引用:
| |
人生充滿了無奈 | 不知道lamina兄是否可以把 winnt.sif 提供出來作參考?不勝感激^_^ |
主題工具 | |
|
類似的主題 | ||||
主題 | 主題作者 | 討論版 | 回覆 | 最後發表 |
【教學】XP NTFS 檔案格式硬碟網芳分享設定法 | simonyang | -- 網 路 技 術 版 | 4 | 2005-06-01 09:17 AM |
【教學】XP 多重開機 + 自動安裝 | lamina | -- Windows 討 論 版 | 149 | 2004-08-30 05:44 PM |
【教學】XP/2000 破解硬體設定 | winkiss | -- Windows 討 論 版 | 3 | 2004-07-19 10:44 AM |
MS Office 自動安裝 | lung_roy | -- OFFICE 相 關 軟 體 討 論 版 | 0 | 2002-04-02 09:59 AM |
多重開機...求救... | edc | -- Windows 討 論 版 | 5 | 2001-10-30 10:50 PM |
XML | RSS 2.0 | RSS |
本論壇所有文章僅代表留言者個人意見,並不代表本站之立場,討論區以「即時留言」方式運作,故無法完全監察所有即時留言,若您發現文章可能有異議,請 email :[email protected] 處理。