Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - cdob

Pages: [1] 2
1
Win8.1 SE HomePage / Re: Migrating from Win10H on Surface 3
« on: August 31, 2017, 06:06:55 PM »
The file Surface3_WiFi_Win10_161250_0.zip contains a lot of drivers. There is a Win8 file available too.
I suggest to add the drivers step by step, as less as possible.

Drivers\System\GPIO
Drivers\System\I2C
Drivers\Display\SurfaceTouchScreenDriver
Drivers\Network\WiFi

View device manager details.
Which .inf and .sys files goes to the Surface TouchScreen Device?
Are this Windows default files or addional files?

2
Win8.1 SE HomePage / Re: Migrating from Win10H on Surface 3
« on: August 31, 2017, 10:58:37 AM »
It's a 64 bit UEFI implemenataion. Yes, use 64 bit OS and drivers.
Neither Windows 8 or Winows 10 incluedes GPIO and I2C drivers by default, Hence add them yourself.
You may try both Win 8.1PESE or Win10PESE. I don't know details out of memory, onscreen keyboard is a OS function and may be supported.
After boot, you may disconnect the PE media and connect another USB device.

3
Win8.1 SE HomePage / Re: Migrating from Win10H on Surface 3
« on: August 31, 2017, 09:49:47 AM »
Run Windows 10, open the device manager, change view per connection.
Are keyboard and mouse childs from GPIO or I2C controller?

Build a Win10PESE.
Open the Driver Integration plugin. Add GPIO and I2C drivers to %GlobalTemplates%\Drivers_x64\

Inlclude the network driver the same way.

https://www.microsoft.com/surface/en-us/support/install-update-activate/download-drivers-and-firmware-for-surface?os=windows-10
http://www.microsoft.com/en-us/download/details.aspx?id=49040
Surface3_WiFi_Win10_161250_0.zip

Did you tried USB hub connected to the USB port?

4
Win10 / Re: Adding x86 PAE to Win10PE, to used 4GB or more ram
« on: March 16, 2017, 05:19:45 PM »
But I do have a question, did this work for you on a Windows 10 x64 bit kernel ----because, the Windows 10 32bit kernel is limited to 4GB !
X86 is 32 bit.
Yes, it works at 32 bit kernel.

The 32 bit kernel is not limited technically, but truncated artificial.

https://msdn.microsoft.com/en-us/library/aa366778.aspx
X86 client versions with PAE enabled do have a usable 37-bit (128 GB) physical address space.

Therefore all 32 bit kernel can access 128 GB RAM.

Be carefull, some third party (graphic card) drivers may not support this.
Try it without adding own graphic card drivers.
Win 8 and Win 10 x86 install.wim ProductPolicy:
Kernel-WindowsMaxMemAllowedx86 4096: max 4 GB RAM

Win 8 and Win 10 x86 boot.wim ProductPolicy:
Kernel-WindowsMaxMemAllowedx86 65535: max 64 GB RAM
If you boot a default 32 bit DVD, then 64 GB RAM are available.

Be careful, some third party graphic card dirvers will fail.
Try it without adding own third party drivers.

5
Win10 / Re: Adding x86 PAE to Win10PE, to used 4GB or more ram
« on: March 15, 2017, 12:53:37 PM »
Given different informations, I assume max 128 GB RAM at a x86 PAE system.

ProductPolicy.script is a rip of from 2-Config.script adjusted with ProductOptions:
Kernel-RegisteredProcessors          64
Kernel-MaxPhysicalPage           131072
Kernel-WindowsMaxMemAllowedx86   131072
Kernel-NativeVHDBoot                  1

The settings works at a 32 GB RAM machine.


ProductPolicy.7z
https://www.sendspace.com/file/2kehca
Add this to the Tweaks folder.

The default kernel and hal files are used, no need to patch them.

6
Win10 / Re: Adding x86 PAE to Win10PE, to used 4GB or more ram
« on: March 06, 2017, 10:22:57 AM »
Which hardware do you use?

Can you clarify: how much RAM is possible at a x86 Win 10? I'm confused about different informations.
64 GB, 128 GB, more?


Win 7 x86 boot.wim ProductPolicy:
Kernel-WindowsMaxMemAllowedx86 131072

Win 8 and Win 10 x86 boot.wim ProductPolicy:
Kernel-WindowsMaxMemAllowedx86 65535

If you boot a default x86 boot.wim, then 8 GB RAM is available at a 8 GB RAM machine.

Kernel-WindowsMaxMemAllowedx86 131072 set at x86 Win10PESE, 8 GB RAM is available at a 8 GB RAM machine.
The default kernel used.

https://msdn.microsoft.com/en-us/library/aa366778.aspx
X86 client versions with PAE enabled do have a usable 37-bit (128 GB) physical address space.

https://en.wikipedia.org/wiki/Physical_Address_Extension
Currently 48 bits of virtual page number are translated, giving a virtual address space of up to 256 TB.

https://blogs.technet.microsoft.com/markrussinovich/2008/07/21/pushing-the-limits-of-windows-physical-memory/
the PFN database on a 128GB system requires about 980MB ... making that a reasonable cut off

7
Win7PE SE HomePage / Re: USB 3.0 driver issue on Haswell Laptop
« on: March 01, 2017, 09:41:08 AM »
Fernando maintains a driver collection and provides a modded Intel iusb3xhc.inf.
The drivers are tested at different hardware. Should work at a PE enviroment too.
http://www.win-raid.com/t834f25-USB-Drivers-original-and-modded.html

A updated RemovableDeviceUSB3_v24.7z
https://www.sendspace.com/file/47trpw

8
Plugins / Re: Additional Files, FileCopy and Unicode file names
« on: February 07, 2017, 10:27:36 AM »
If Jörg fixes the issue with characters outside the BMP, then maybe cdob can add the unofficial patches (storage optimization etc.) and build a recent cygwin version of mkisofs with support for iconv and any Unicode character, similar to oscdimg.
Jörg inlcuded and adjusted the patches  (storage optimization and upper file case). No idea about characters outside the BMP.
There is no need for a unofficial version anymore, I quit the support after 12 years.
The official cdrtools support the features now. -force-uppercase was renamed to -no-allow-lowercase.

From AN-3.02a07
https://sourceforge.net/projects/cdrtools/files/alpha/

Quote
mkisofs: New option -no-allow-lowercase allows to revert the effect to
-allow-lowercase from macro options like -untranslated-filenames or
-iso-level 4

mkisofs: New option -duplicates-once to hard link identical files even
on non POSIX platforms.
The code was modeled similar to the code from
Alex Kopylov cdrtools@bootcd.ru but better fits into the idea of
current versions of mkisofs


https://www.student.tugraz.at/thomas.plank/

9
The running circles indicates a driver or hardware issue. No idea about real reason.
Does works a default Windows 10 DVD boot.wim with extracted files?

My end goal is to actually apply the PE results to a VHD image
How is the VHD image used?
Is it used by a virtual machine, hence a internal disk at the running virtual machine?
Then you may use InRAM approach still.
How much RAM is available at the virtual machine?

10
Thanks for report. I guess you used e.g.

Code: [Select]
title   Default settings 32 (Runs from RAM). > 312MB
kernel /pmagic/bzImage edd=off load_ramdisk=1 prompt_ramdisk=0 rw vga=normal loglevel=9 max_loop=256 vmalloc=384MiB
initrd /pmagic/initrd.img /pmagic/fu.img /pmagic/m32.img
lock
 
title   Default settings 64. > 312MB
kernel /pmagic/bzImage64 edd=off load_ramdisk=1 prompt_ramdisk=0 rw vga=normal loglevel=9 max_loop=256 vmalloc=384MiB
initrd /pmagic/initrd.img /pmagic/fu.img /pmagic/m64.img
lock

Does works this exmaple?

11
A 2013 version is supported.
Can you name the currently used version number? The 'latest version' may lead to false information in future.

Adjust menu.lst or grub.cfg yourself.
Can you post currently used Parted Magic menu entry?
Append fu.img and m32.img/m64.img to the initrd line.

http://theoven.org/index.php?topic=1659.0
http://askubuntu.com/questions/636952/help-creating-custom-grub2-entry-for-parted-magic-2015-have-working-2013

12
Win10PE SE HomePage / Re: Strange Diskpart error.
« on: May 08, 2016, 05:50:53 AM »
Crystal ball:

double click runs at current directory %SystemRoot%\system32
Diskpart.exe is found at current directory

.csv menu runs at another directory.
Path is not defined, broken crysal ball?
Diskpart.exe is not found at current directory and not found at path.

As for debug, edit WinInstall.cmd, add path and pause
path
pause

Define a full qualified path diskpart.exe at WinInstall.cmd
%SystemRoot%\system32\Diskpart.exe

13
Please note that I am using Win7PE x86. Unfortunately the mouse and keyboard still not working on Dell servers...Any idea on why this happened..?
Do you use USB 2.0 or US B 3.0 ports at the server?
Any other OS insalled? Can you check device manager connections?

It's a Dell, this is asking for a strange BIOS, strange USB timing settings.
Verify used USB controller first.

Series 7/8 refers to the Chipset Family, the manufacturer uses this names.

USB 3.0 eXtensible Host Controller Driver for Intel® 7 Series/C216 Chipset Family
https://downloadcenter.intel.com/download/21129/USB-3-0-Driver-Intel-USB-3-0-eXtensible-Host-Controller-Driver-for-Intel-7-Series-C216-Chipset-Family
Version: 1.0.10.255 (Latest) Date: 2/3/2014


PowerEdge FC630 technical specification
http://i.dell.com/sites/doccontent/shared-content/data-sheets/en/Documents/Dell-PowerEdge-FC630-Spec-Sheet.pdf
Chipset: Intel C610 series

USB 3.0 Driver: Intel® USB 3.0 eXtensible Host Controller Driver for Intel® 8/9/100 Series and C220/C610 Chipset Family
Version: 4.0.4.51 (Latest) Date: 1/29/2016
https://downloadcenter.intel.com/download/22824/USB-3-0-Driver-Intel-USB-3-0-eXtensible-Host-Controller-Driver-for-Intel-8-9-100-Series-and-C220-C610-Chipset-Family

The historic USB3 script dosn't support your hardware.
Disable the USB 3 script and integrate the drivers yourself: Driver Integration script

14
Plugins / Re: Additional Files, FileCopy and Unicode file names
« on: April 08, 2016, 06:25:50 AM »
We may use Cygwin Internationalization https://cygwin.com/cygwin-ug-net/setup-locale.html instead of -input-charset -output-charset

Cygwin supports environment variables LC_* to define locale settings.
Mkisofs uses this locale cygwin definition.

set LC_CTYPE=C.UTF-8
set CYGWIN=acl nodosfilewarning
mkisofs.exe -iso-level 4 -udf -o ../foo.iso .
Setting input-charset to 'UTF-8' from locale.


Another example: UDF file system only.
set LC_CTYPE=C.UTF-8
mkisofs -hide "*" -udf -v -o ../foo.iso .
Booting not tested: will fail at setupldr.bin, may work at bootmgr

Current cdrtools https://sourceforge.net/projects/cdrtools/files/alpha/
Sorry, quick and dirty web space
cdrtools-3.02a06-bootcd.ru-mkisofs_Iconv.7z
http://expirebox.com/download/5a5131cb2aaafa0fc59fe02aa0fb7a9b.html


Gena
Do you expect and use ISO9660 or UDF file sysem?
Did you enable the UDF script and set to automatic mode?
I don't remember: which file system does XP PE prefers at a ISO9660 / UDF bridge CD?

15
Plugins / Re: Additional Files, FileCopy and Unicode file names
« on: April 04, 2016, 07:20:09 PM »
add the unofficial patches (storage optimization etc.) and build a recent cygwin version of mkisofs with support for iconv and any Unicode character
Good charset investigation and summery, congratulations.
I stand by to adapt the build, no promise, let's see.

Quote
similar to oscdimg.
I'm using cdrtools since the year 2000 and like mkisofs.
Nontheless, if someone likes to create a plain WinPE and AIK is installed: I recommend oscdimg today. It's the native solution.
A multi boot ISO is another question: oscdimg dosn't support rock ridge.

16
Separated versions, i.e., one AIO for Windows 7, another one for Windows 8.1, etc. Don't want to mix Windows versions.
What about USB? Do you use three different USB disks, do you like to add all windows versions to one USB disk?
 
Quote
a Windows 7 AIO with double architecture folder...
Windows 7 setup.exe dosn't support x86/x64 folder.
Windows 8 and up setup.exe does support x86/x64 folder.

17
Win8.1 SE HomePage / Re: Combine x64 & x86 in one ISO? (UEFI & BIOS)
« on: October 26, 2014, 06:58:22 AM »
And I hope that this combined ISO can boot to the x86 version on 32-bit UEFI system (Asus T100), x64 version on 64-bit UEFI system (Venue 11)?
There is no optical drive included.
How do you boot a ISO file? Do you write a CD, DVD or other?
Do you use a USB optical drive?

What about a USB storage disk?

create a 2.88 mb floppy image and hexedit files:
\EFI\BOOT\BOOTIA32.EFI: bootmgr.efi to bootmgr.x86
\EFI\BOOT\BOOTX64.EFI:  bootmgr.efi to bootmgr.x64

Use this floppy image as EFI boot image.

Add both versions to \efi\microsoft\boot\bcd and create entries for renamed boot.wim.

\Programs folder name is used at x86 and x64 PE. How to solve this?
Incldue all files to boot.wim?

18
Win8.1 SE HomePage / Re: USB Audio DAC doesn't work
« on: August 13, 2014, 07:02:35 AM »
The script Audio does include wdma_usb.inf already.
A simple USB sound card should work out of the box.

Again:
Which USB sound device do you use?
Which HardwareID and compatileID refers to the USB sound device?
Which Windows files do you use at running windows?

19
Win7PE SE HomePage / Re: problem in creating the iso file
« on: July 28, 2014, 09:12:28 AM »
I get from friend a win7  x86 ( I have a x64  )  unzip in to to folder  and run the  little version using this version  and the problem  with
the mkisofs disappear
Which windows files did you used previously? Any OEM version?

One again: which mkisofs files do you use?
Do you use the version from Win7PE_SE_Small_2014-05-19.7z? This is a 7-zip file, not a zip file.
Do you use another version?

Quote
any idea what can  cause the error message
No idea. Could be source files or a protection software.

As for debug: open a command prompt and run
Code: [Select]
cd /d D:\Win7PE_SE_Small_2014-05-19\Temp\Win7PESE
CreateISO_Debug.cmd
Post the output. Do it.

20
Win7PE SE HomePage / Re: problem in creating the iso file
« on: July 28, 2014, 07:47:27 AM »
i try to build    a project  for now using the  small version
I  download the  mkisosf zip file   and put  the exe and the dll in "D:\Win7PE_SE_Small_2014-05-19\Projects\Win7PESE" folder  amnd also in  "D:\Win7PE_SE_Small_2014-05-19\Projects\Tools" (  i am not sure it is OK )
Why do you add mkisofs files yourself?
Which mkisofs zip file did you download?
Which files did you copy? List all file names.
Run a 'mkiosfs -version' at command line and post the output.

Pages: [1] 2
Powered by EzPortal