cdob
Content Type
Profiles
Forums
Events
Everything posted by cdob
-
KMDF Version History http://msdn.microsoft.com/en-us/library/windows/hardware/ff544309.aspx KMDF version 1.11 is supported at Windows 8, but not at Windows 7. Dism dosn't include files inside wdfcoinstaller01011.dll, KMDF is not updated. Update KMDF files yourself. Or try a old driver package, but add HardwareID PCI\VEN_8086&DEV_9C3A to heci.inf. A old driver may work or fail. https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=22597 Version: 9.0.5.1367 No KMDF update required, but without official Series 9 support.
-
http://www.asus.com/Motherboards/P7P55D/specifications/ A middle age Series 5 Chipset: P55 Express Chipset Intel changed driver at the same time. http://www.asus.com/Motherboards/P7P55D/HelpDesk_Download/ You may use both Matrix Storage or Rapid Storage driver model. Goto device manager, goto mass storage controller, list details. Which HardwareID does match? Well, I've another experience. msahci.sys works at AMD and Intel AHCI mode. E.g. installtion with msahci.sys works at a PCI\VEN_8086&DEV_1E03&CC_0106 on a new SSD drive here.
-
Which motherboard do you use? Read the motherboard specs and the motherboard manual. Which SATA connector is connected to which storage controller? Matrix Storage refres to old chipset wiht a ICH7, ICH8, ICH9 http://www.intel.com/design/chipsets/matrixstorage_sb.htm Rapid Storage refres to current chipset. http://www.intel.com/content/www/us/en/architecture-and-technology/rapid-storage-technology.html Do you use AHCI or RAID mode? Windows 7 default drivers should work at AHCI mode for controller embedded in the chipset. At basic installed windows open device manager, select a device details and read the HardwareID. This hints used hardware. Search for this HardwareID.
-
Yes, this is possile. Actually there are predefined names ntdetect.com, setupldr.bin, txtsetup.sif and folder I386. win51* is referenced in txtsetup.sif. Another approach: configure BootPath and do not copy further boot files. http://www.msfn.org/board/topic/142221-multiboot-dvd-boot-folders-error/#entry911471 http://www.msfn.org/board/topic/126480-windows-xp-professional-x64-sp2-in-multiboot-dvd/#entry814566 http://www.msfn.org/board/topic/126480-windows-xp-professional-x64-sp2-in-multiboot-dvd/#entry893775 Either copy files .\XP32\I386\* .\XP32\NTDETECT.COM .\XP32\SETUPLDR.BIN .\XP32\TXTSETUP.SIF Or rename files at I386 folder. Hexedit setupldr.bin according. .\XP32\I386\* .\XP32\I386\XP_.COM .\XP32\I386\XP_.BIN .\XP32\I386\XP_.SIF Yes, that's true. The links refers a gsar example and a grub4dos example.
-
http://www.win-raid.com/t317f23-Intel-Series-C.html#msg4210
-
Thanks for the information. A Win8.1 UP1 DVD bootet: C:\wimboot>copy d:\sources\install.wim C:\wimboot>Dism /Apply-Image /ImageFile:C:\wimboot\install.wim /ApplyDir:F:\ /Index:1 /WIMBoot Unsupported operation. Check that the WIMBoot applied image is WIMBoot compatible. Error: 0xc1440137 Contrary: WinNTSetup applies the same file C:\wimboot\install.wim to drive f: as wimboot. Windows does boot from the wim file. Awesome, good work.
-
Can you clarify?Yes, wimboot works, given a file *.wim already at wimboot format. Thanks. What about a msdn DVD install.wim or a install.esd? Do you export this files to wimboot format too? I get a error message at <DVD:>\sources\install.wim: "Applying System image failed!" A example to clarify the question md W:\Scratchmd W:\Win8Dism /Export-Image /WIMBoot /SourceImageFile:D:\sources\Install.wim /SourceIndex:2 /DestinationImageFile:W:\Win8\wimboot.wim /scratchdir:W:\Scratchrd W:\Scratch
-
No hardware monitoring software is showing me my GPU temperature or fa
cdob replied to vipejc's topic in Software Hangout
http://www.techpowerup.com/forums/threads/cant-get-gpu-temp-to-show.84032/ https://www.sapphireforum.com/showthread.php?23466-What-is-a-proper-(GPU)-temperature-for-quot-Sapphire-X1650-Pro-quot-graphics-card The X1650 does support temperature monitoring, however some graphic card manufacturer disabled this feature. -
enable AHCI after XP install
cdob replied to intzepatorii's topic in Windows XP Media Center Edition
This HardwareID refers to ICH9 and dosn't match a H81 chipset. ven_8086&cc_0106 refers all Intel ACHI controllers. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&cc_0106] Yes, this is the other approach. Thanks for confirmation: isator.sys v11.2.0.1006 works at a H81 chipset. -
Setupldr.bin searches \I386\CDROM.SY? at textmode and won't find a lower case file, textmode will fail. Yes, cdfs.sys reads Joliet. cdfs is loaded at installed windows. What about cdrtools-3.01a23-win32-bin.zip? http://www.student.tugraz.at/thomas.plank/index.html Neither Nlite nor MS care about case at hotfix integration. Both expect uppercase at following step. I doubt file case as a reason. No, Windows can't read rock ridge. If possible avoid rock ridge at XP installation cd. Grub4dos maybe case sensitive still. Does filenames within menu.lst has to match case at DVD? Iso9660 Level 3 proihibits lowercase, hence mkisofs uppercase the name. Compare the name at ISOBuster. Textmode can't read joliet, cdfs.sys is not active that erarly. -allow-lowercase allows lower case: it's preservers case from the hard disk: uppercase names goes uppercase, lowercase names goes lowercase
-
http://en.wikipedia.org/wiki/ISO_9660http://de.wikipedia.org/wiki/ISO_9660 ISO9660:1988 is a standard. http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=17505 ISO9660:1999 is a draft and won't get a standard anymore. No Windows support this on purpose. A lot of limitations are removed. Be careful: you may shoot your own foot. Umlaute are impossible at ISO9660:1988, and possible at ISO9660:1999. Yes, worst-case compatibility, but required if you need ISO9660 Umlaute. What about? rem UpperCase XP files at hard diskrem Win32 Console ToolBox http://stevemiller.net/apps/ren F:\n-Lite-Temp\i386 I386filecase.exe /u F:\n-Lite-Temp\win*filecase.exe /u /s /d F:\n-Lite-Temp\i386 Grldr may search GFX-BOOT.GFX or gfx-boot.gfx. I don't know.Just because menu.lst is found both cases, dosn't require this for GFX-BOOT.GFX. chcp cp850 Does exist ISO9600 uppercase filename \I386\CDROM.SY?Which mkiosfs -version do you use currently? Yes, ImgBurn creates nice ISO images too.
-
Yes, that's it to get Umlaute. What happens at textmode setup? Did you uppercase required files at hard disk first and build the ISO next?
-
Summerize this to: uppercase required files yourself set LC_ALL=en_US.CP850 mkisofs -iso-level 4 do not use Joliet
-
Strange, seems to ignore Joliet fileystem. Compare file systems at ISOBuster. The free version supports ISO9660, Joliet and RockRidge. Cygwin/Iconv can handle Umlaute at ISO9660:1999, -iso-level 4 nowadays. Haven't done this in years. Seems to be some fun. Back then I used a environment variable: set LC_ALL=en_US.CP850Simple example added: "mkisofs -iso-level 4 -o o.iso ." Umlaute are listed correctly, given CP850 is set at windows. That's the default codepage at a german installation. Which files do you use? http://cdrecord.berlios.de/private/cdrecord.html ftp://ftp.berlios.de/pub/cdrecord/alpha/win32/ ftp://ftp.berlios.de/pub/cdrecord/alpha/ Jörg offers source code only nowadays, last win32 binaries are from 2001. http://www.student.tugraz.at/thomas.plank/index_en.html Thomas offers binaries since then. That's good, because support won't be within forum rules. I've to correct: -allow-lowercase allows lowercase. -iso-level 3 -N -D -d -relaxed-filenames -allow-lowercase -allow-multidot -joliet-long Post #12 refers FileCase.exe http://www.911cd.net/forums//index.php?showtopic=4382&view=findpost&p=26119 Uppercase XP files in root, all folder and files within I386 Core boot files has to be below 4 GB LBA, the ISO file can be bigger.
-
Yes, requirements are changed: grldr finds a ISO9660 filename /MENU.LST and /menu.lst. A uppercase or a lowercase file is found. @whocares02 Step back one step. Rephrase the question. You like to create a Multiboot-DVD. So far I understand grub4dos as bootloader and adding Windows XP. Which multi boot parts do you like to include too? There is no general filesystem/filecase advise for a Multiboot-DVD. E.g. a WinPE1 uses different filenames as a XP installation CD. There are different solutions based on different included parts. Clarify your needs.
-
That's a outdated version, name used version string always. Use a current one. I'm using hardlinks at mkisofs cygwin. Remember setupldr.bin searches uppercase names: I386 not i386.
-
The suggestion was to create a ISO image first, not to edit it and burn it with ImgBurn, The boot record may be grldr, actually first four virtual sectors prefered. Read again: -b grldr reference the grub-boot-record: grldr itself is the boot record.
-
@whocares02 To allow lowercase use option mkisofs -relaxed-filenames -iso-level 4 uncludes -relaxed-filenames http://www.msfn.org/board/topic/171350-textsetup-wont-accept-nlite-dvd/page-2#entry1072315 Be aware: some bootloader expect uppercase at ISO9660: setupldr.bin and bootmgr. Uppercase textmode boot files at hard disk first. Or use a ISO9660 MENU.LST and RockRidge menu.lst. You may edit the embedded menu.lst too. Use a current grub4dos: grub4dos-0.4.5c-2014-01-17.7z http://code.google.com/p/grub4dos-chenall/downloads/list Uppercase requirements may have been changes, don't remember details anymore.
-
Well, this relates to Win7, this is not XP. XP installation approaches won't work here. Search for a Win7 solution elsewere http://reboot.pro/forum/66-grub4dos/ http://bbs.ipauly.com/ Or start a new thead. http://www.msfn.org/board/forum/165-windows-7/
-
No, do not add AMD AHCI files at XP: do not include amd_sata.sy?. This file refers to 2003. http://www.gigabyte.us/products/product-page.aspx?pid=4709#dl Add the "AMD RAID/AHCI Driver (Preinstall driver, press F6 during Windows* setup to read from floppy)" as textmode files only.
-
The BIOS suuports keyboard device like devices only. A UEFI firmware supports a mouse too.
-
Bcdedit.exe works both at XP and Windows 7. So does BOOTICE http://bbs.ipauly.com/viewtopic.php?f=2&t=2&sid=ebc27aec23a8eb21006e07ab6f3b01cb
-
If I rember correctly, nfocre expect SP1 at least. Contrary try XP SP3.
-
Neither do I know. Try the files from the folder sp33411\IDE\WinXP\sataraid\ If you use nLite already, then try Fernando's package too. But only as another step. Do not add both packages.
-
Well, I don't pocess the hardware and have to guess. No step-by-step solution. Without manufacturer support, you have to find a solution yourself. The given thread: http://h30434.www3.hp.com/t5/Notebook-Operating-Systems-and-Software/General-XP-Downgrade-Guide-for-HP-Laptops/td-p/83267 refers "Model BELOW dv65xx and with AMD processor refer to dv6000Z drivers." Here http://h10025.www1.hp.com/ewfrf/wc/softwareCategory?cc=us&dlc=en〈=en&lc=en&os=228&product=3224052#N301 Try this Chipset driver. How do you run nLite? 7-zip does expand HP sp33411.exe. Or try "32bit nForce LEGACY drivers v6.99 mod by Fernando" http://www.msfn.org/board/topic/51140-integration-of-nvidias-nforce-raid-and-ahci-drivers/ Yes, this is to be expected. I doubt strongly a Intel SATA AHCI driver at a AMD CPU motherboard.