chee

well I've found the certificate file ntoskrnl.exe ntkrnlpa.exe bear, but I don't know how to transfer it to the edited files with new boot image imgerged

I've merged vista boot image into ntoskrnl.exe ntkrnlpa.exe but, these modified files can't pass Digital Signature Verification at bootup anyone know how to endow the modified files with the digital signature of original files? or how to disable Digital Signature Verification at bootup? Thanks

to DigeratiPrime: I would like to realize the picture posted as the bootscreen by you, by editing the kernel file of vista. since i'm not good at Photoshop and I am busy with my application for PH.D study in USA, I need some time. I'll share it with you

well, I got it done. hereunder is how: Scheme 1: move %systemroot%/bootmgr, /boot/bcd into another directory,then boot from dvd, in this case vista dvd COULD NOT repair bootup Sheme 2: move these two files back to their original places, boot from dvd, choose "startup repair", then boot into vista. this time bcdedit recognizes the bcd file, which is I:\>bcdedit /store i:\boot\bcd /enum active Windows Boot Manager -------------------- identifier {bootmgr} device boot description Windows Boot Manager locale en-US inherit {globalsettings} default {ntldr} displayorder {ntldr} {4c284500-83e1-11db-92d9-cd928292f644} toolsdisplayorder {memdiag} timeout 10 Windows Legacy OS Loader ------------------------ identifier {ntldr} device partition=C: path \ntldr description Windows XP Bilingual custom:47000005 301989892 6 Windows Boot Loader ------------------- identifier {4c284500-83e1-11db-92d9-cd928292f644} device partition=I: path \Windows\system32\winload.exe description Windows Vista Ultimate osdevice partition=I: systemroot \Windows then i deleted the entry for xp *** I:\>bcdedit /store i:\boot\bcd /delete {ntldr} /f The operation completed successfully. now the bcd is: I:\>bcdedit /store i:\boot\bcd /enum Windows Boot Manager -------------------- identifier {bootmgr} device boot description Windows Boot Manager locale en-US inherit {globalsettings} displayorder {4c284500-83e1-11db-92d9-cd928292f644} toolsdisplayorder {memdiag} timeout 10 Windows Boot Loader ------------------- identifier {4c284500-83e1-11db-92d9-cd928292f644} device partition=I: path \Windows\system32\winload.exe description Windows Vista Ultimate osdevice partition=I: systemroot \Windows but I still can't successfully run the "import" command, and the error is I:\>bcdedit /import i:\boot\bcd The store import operation has failed. The volume does not contain a recognized file system. Please make sure that all required file system drivers are loaded and that the volume is not corrupted. I could not figure out the reason for this last issue, since the entry point is identifier {4c284500-83e1-11db-92d9-cd928292f644} where/how to add fs attribute to this id, ie, add file system spec to it as "ntfs". yet, vista goes smoothly any further ideas? (i would recommend an os scheme that deploys different oses on different primary partitions, for those in need of more than 5 oses on a single hdd, this scheme is impossible and the fifthe and the sixth, ... should have to be installed on extended (logcial partitions), such a scheme would make other boot record intact when operating on a single partition since not all boot records are jammed into the mbr of hdd which is 001 in chs)

i'll try to delete the bcd files and boot from dvd to repair the boot loader and report to you any progress

To MaTavish: to my knowledge the progress bar is a gif animation that is employed while booting, you can use resourcehacker to open ntoskrnl.exe and locate this gif, also any system animation such as the one you see when executing a "delete" command (the animation of tearing files into pieces and send them to the recycle bin) could be found in shell32.dll (also could be opened by resource hacker) for windows oses, boot progress bar is in the kernel file or in shell32.dll hope this would help and any corrections are welcomed

1. all the operations are on a sinlge HDD 2. I've used acronis trueimage 9.0 (with serial and hence full functionality) 3. I intended to erase the "earlier versions of windows" option from the bootmenu list, since I use linux grub to boot each of the 3 oses on 3 seperate primary partitions (hda1 xp, hda2 linux with grub on, hda3 vista) 4. I'll try imageX the only problem acronis trueimage causes is the unbootability, from the practices it could be infered that vista boot record resides only on the mbr of the target partition, ie. for my case is on mbr of hda3. not as was said on the mbr of the whole HDD, ie. chs=001 since my restoration operation never makes xp unbootable and never srew grub, since grub stage 1 is injected in chs=001 thanks for all your help

Operations: 1. install vista by simulating iso from xp on hda1 (the first primary partition) onto hda3 (the third primary partition) 2. backup vista (on hda3, with drive letter "I") by Acronis Trueimage, resize hda3 from 7g into 6g, restore backup image file onto resized hda3 3. now comes the problem: \windows\winload.exe the selected entry could not be found the application is missing or corrupt. 4. I burned the iso file into a dvd, set hda3 active, boot from dvd rom, choose (repair windows) after repair, windows vista booted smoothly, the os menu list contains "earlier versions of windows'. but: when i select ""earlier versions of windows", the screen goes black and the pc reboots 5. operation in vista i booted into vista and run bcdedit /enum all and got the report: the boot configration store could not be opened, the system can not find the file specified. I also tried: 5.1 bcdedit /delete {ntldr} /f but got: the specified entry identifier is not valid. the parameter is incorrect. I also tried Vistabootpro 3.1, but got: There is currently 0 OS(s) installed in the boot manager. Current timeout before default boots: 0 Default OS: Hereunder is a list of commands tried and reports got: I:\>bcdedit /enum all The boot configuration data store could not be opened. The system cannot find the file specified. I:\>bcdedit /delete {ntldr] /f The specified entry identifier is not valid. The parameter is incorrect. I:\>bcdedit /import i:\boot\bcd The store import operation has failed. The volume does not contain a recognized file system. Please make sure that all required file system drivers are loaded and that the v olume is not corrupted. I:\>bcdedit /v The boot configuration data store could not be opened. The system cannot find the file specified. ----- i could not find the entry for xp on hda1 in the form of : ( bcdedit /delete) {cbd971bf-b7b8-4885-951a-fa03044f5d71} ( /cleanup) any ideas? thanks

to DigeratiPrime: is the picture in your post your boot screen? could u please email me one copy chee.chen@yahoo.com thanks

yes, but sometimes it's not desirable to install each vista on each pc, spending about 20 minutes each i've resized the vista-residing partition,restored the acronis image 9the slimmed vista) and vista bootup got jammed again saying that: winload.exe could not be loaded. and vistbootpro shows no os at all sometimes it's better to get deeper into the booting process of oses. my practices show that: 1. for a emulated vista installation onto another primary partition, the existing mbr is UNCHANGED, the bootmanager and booting record on the target partition are SEPARATED. any change in either of these above two items would probably cause INCONSISTENCY and put vista boot into TROUBLE. 2. since vista is shipped with almost all existing drivers for hardware support, there should be no worry on restoring vista image on pc's, since a reboot would always put the needed drivers ready on the target pc's. the only thing that needs care is the BOOT RECORD. 3. i'll burn the iso into dvd and try to directly install vista on the primary partition hda3 and merge the bootmanger and bootrecord into hda3, not separated as i was troubled before hehe

AlYum gives the right answer: the original vista could not find an entry point after the jmp command in the mbr is executed tonight i tried vLite and slimmed the vista installation iso file into a single vista ultimate installation file and reinstalled vista thanks to you both

acronis trueimage could "pave" a 7g image into a 6g parition by recalculating the start/end CHS values on the target parition. i could boot into xp. the error report is: entrypoint could no be found yet: winload.exe is right in /system32 so it seams the boot record on the original hda3 has been erased during resizing. the most wird thing is that: i never got a "boot repir (or the like) " option when emulating the iso file and click on setup.exe. i got only two options: "install windows" and "check compatibility online". even if i continued to click "install windows" there is NO "boot repair (or the like)" option It is true that only by burning this iso file onto dvd and booting from dvd-rom could i get an option like "boot manager repair" I've tried bcdedit, it returns a list WITHOUT ANY OS also i've tried bootsect.exe with parameter nt60 both failed While one thing is confirmed, Vista don't rewrite or make changes to mbr, since ghosting xp back to hda1 will erase the original boot menu created by vista installation and restore xp correctly. i've tried this out

1. disk geo: hda1 primary, fat32, for windows xp hda3 primary, ntfs, for windows vista 2. installation mode: install vista directly via simulating iso as cd-rom in windows xp into hda3. so the boot files of vista reside on hda1 3. problem discription 3.1 i have installed via the same method, under the same disk geo a vista, and activated it. then i backed up this activated vista via acronis trueimage. then i resize hda3 into 6g since vista took about 7g space, then i restore the backup vista to hda3. 3.2 when i choose windows vista from the os menulist, i got the error: winload.exe can't locate the entry the application is corrupted or missing 3.3 is there a way to repair vista boot without burn the iso into a DVD? Thanks

OS spec: win xp sp2 recently at each startup after shutting down the pc by the "shut down" option, there's a fence of bars ( like the one appears at booting-up after hibernating a pc), indicating the booting up progress how come this bothers? progress bars appears at booting up after hibernation, but not after a norm "shut down" any ideas? Thanks

recently i've changed my xp eng into xp deutsch, yet ie7 beta 3 didn't seem to perform a normal upgrade since after upgrade the shell was missing. I've searched online for ie7 beta2 deutsch, but all links led me to ie7 beta3 deutsch. could someone mail me an ie7beta2 at: chee-chen@163.com ? thanks in advance bow~

thanks to Takeshi Sa'N! I'm following the link

1. prob. description: set software policy, that is, restrict certain users to their execution authorization 2. os desc'p: win xp pro sp2 3. why bothers: xp is easy to use, but unlike unix/linux, it comes without default authorizations on executable and folders ---- any information on this? Thanks in advance!

thanks! I've tried r-studio and it really helped!

recently i mistakenly formatted my ext3 partition into FAT32, thus destroy precious data therein. is it possible to recover data in the original ext3 partition if the newly formatted partition is kept unwritten thereafter?? thanks

start service: cdac11ba.exe - fix it!

i've suddenly got this error message: NT users should logon with Administrator rights and run this application again,... restart.. and now lognman dic is disable, regardless of the inserted iso into virtual driver. i did log on as administrator, yet this still didn't improve. any help ???? thanks

"To include the MBR you have to image the disk with COPY or DUMP rather than the partition with PCOPY or PDUMP." this may be right! yet, what i've tried is really an image to partition ghosting, which caused the problem. cause boot info and partition table is stored in MBR so, it seems that: if ghost records MBR, then there will be disaster; else, it's safe. and the only thing left is HAL crossing

Thanks to ICEManND! cause these days i've noticed this subtle change when dumping an image with ghost. my 1st primary partition is with cluster size 2k, but the restored partition is with cluster size 4. since i've never tried to partition the 1st primary partition not according to the default size, i'm not sure whether ghost made this change. also, could i be told how PQ magic resizes the cluster size? does pq magic only change the info in both two copies of fat32 located at CHS: 011 (while MBR is reserved at CHS=001) without rearranging the data on the target partition?

1. problem description: suppose a fat32 partition is with cluste size 2k, ie, 512b*4, and, ghost this partition into an image, now, dump this image back to the source partition, will the original cluste size be reserved?? 2. why this bothers: since storing small files with larger cluster size will result in bigger space waste, and it's alway true that the operating system constains many files of small sizes, hence to be space-efficient, a small cluster size is favored, though this will lead to longer defragmentizing time. --- any suggestion would be appreciated. --- test results: PQ magic could resize cluster size without data loss and partition table change

Thanks to Jaclaz! i've just tried to edit grldr with UltraEditor in hex mode, and the edited grldr crashed. so the only possible way is to download its source and recompile the edited one. i've tried this scheme and succeeded: ----- 1. install wingrub on primary partition 1 2. install real dos 7.1 on primary partition 1, and let dos 7.1 make a dual boot 3. make primary partition 1 active since dos 7.1 needs an active primary partition 4. leave grub for linux intact, grub for linux is installed on primary partition 2, where fedora core 4 resides. ---- it's Jaclaz's suggestion that led to me wingrub and, here again my appreciations.