40 replies to this topic

[John Hensley]

@John Hensley
I run Rescue Boot first time, and it got fatal errors. I see these lines in the log:

{COPY_REG } [LEAVE_PROCESS_SECTION] RetCode = {0x00000000} UnloadRegistry
{COPY_SYSTEM} [ENTER_PROCESS_SECTION] UpdateAndEnableRescueBootDriver
{COPY_SYSTEM} [LEAVE_PROCESS_SECTION] RetCode = {0x00000000} UpdateAndEnableRescueBootDriver
[ASSERTION FAILED] @ line #402 in .\CopySystem.cpp
{COPY_SYSTEM} Current Privilege levels:
{COPY_SYSTEM} 0x0 - SeBackupPrivilege
{COPY_SYSTEM} 0x0 - SeRestorePrivilege
{COPY_SYSTEM} 0x0 - SeShutdownPrivilege
{COPY_SYSTEM} 0x0 - SeDebugPrivilege
{COPY_SYSTEM} 0x0 - SeIncreaseQuotaPrivilege
{COPY_SYSTEM} 0x0 - SeSystemEnvironmentPrivilege
{COPY_SYSTEM} 0x3 - SeChangeNotifyPrivilege
{COPY_SYSTEM} 0x0 - SeRemoteShutdownPrivilege
{COPY_SYSTEM} 0x2 - SeUndockPrivilege
{COPY_SYSTEM} 0x0 - SeSecurityPrivilege
{COPY_SYSTEM} 0x0 - SeTakeOwnershipPrivilege
{COPY_SYSTEM} 0x2 - SeLoadDriverPrivilege
{COPY_SYSTEM} 0x0 - SeManageVolumePrivilege
{COPY_SYSTEM} 0x0 - SeSystemProfilePrivilege
{COPY_SYSTEM} 0x3 - SeImpersonatePrivilege
{COPY_SYSTEM} 0x0 - SeSystemtimePrivilege
{COPY_SYSTEM} 0x3 - SeCreateGlobalPrivilege
{COPY_SYSTEM} 0x0 - SeProfileSingleProcessPrivilege
{COPY_SYSTEM} 0x0 - SeIncreaseBasePriorityPrivilege
{COPY_SYSTEM} 0x0 - SeCreatePagefilePrivilege
{COPY_SYSTEM} Previous Privilege levels:
{COPY_SYSTEM} 0x0 - SeBackupPrivilege
{COPY_SYSTEM} 0x0 - SeRestorePrivilege
{COPY_SYSTEM} 0x0 - SeSecurityPrivilege
{COPY_SYSTEM} 0x0 - SeTakeOwnershipPrivilege
{COPY_SYSTEM} 0x0 - SeManageVolumePrivilege
I guess there is protected storage area in the registry that causes the problem.
Since it is protected, this should be considered as a warning, not a fatal error.

The original error is probably documented earlier in the log file. If you would send me the log files I will take a look to see if we can get it working on your system. Here is a link to instructions for automatically generating a compressed set of the log files and then emailing them to our support email alias.

One quick question before you go to the trouble of sending the log files. Did you allow the setup program to reboot the computer before starting the RescueBoot Wizard? If not you will probably have problems running the Wizard until after you have rebooted the computer.

Thanks,
John Hensley
www.resqware.com

[John Hensley]

Musings/questions:
1) I wonder if the services etc could be used to replace FBWF or BootSDI?

FBWF supplies file based functionality that the RescueBoot drivers do not support. In theory BootSDI could probably be implemented with something like the RescueBoot drivers.

2) I wonder if the filesystem accepts junctioning, eg junctioning an external programs folder to, say, 'x:\Program Files'?

When booted from the RescueBoot CD the underlying filesystem in the image file is NTFS so it should support anything that is supported on the original end user system used to create the RescueBoot CD. In fact, when RescueBoot creates the hard disk image file it compresses most of the files using NTFS compression to reduce the size of the image file and speed program and file loading when running from the CD.

3) Is writable space on BOOTIMG.BIN reserved in the actual image (like BootSDI) or in ram (like FBWF)?

Writeable space is reserved in both places. The image file is laid out as a standard hard drive containing a single NTFS partition that has about 32MB of free space and writeable files on it. When the driver creates the virtual drive it allocates 32MB of memory to allow files to be created in the free space and writeable files to be over-written.

John Hensley
www.resqware.com

[John Hensley]

Please correct the url of your links. You used backslashes instead of slashes, not all browser are ok with that.

Thanks for the heads up on the url links. I've fixed the links as suggested.

PS: Can it be, that i remember your name from Qualcom?

I've never been associated with Qualcom. Couldn't you tell from my url links that I'm originally from Microsoft. That's why I always forget that there are browsers other than IE. I've also done a lot of work for Iomega in the past.

Regards,
...John

[thunn]

Ok. even after repackaging the setup, the program itself still recognizes a probem with xp sp3, very complete job, John! I'll just run it on a virtual pc.

[John Hensley]

Hi John, welcome to our community!

Thank you for personally answering our doubts - this is a very professional work indeed.

Currently the only options we have to use a non-PE XP environment in read only media are based on MS files (Win2003 SDI/ISO Ram boot & XP embedded) and non MS as Diskless Angel (trial/commercial) for example.

Since these drivers are made available for free - would you allow us to use them in XP based projects discussed here?

Author rights and credits properly respected and mentioned of course.

At this time I'm still not sure what I should do with the technology. I'm currently giving RescueBoot licenses away for free to get feedback to use in deciding what direction to take going forward. If I decide that it's not worth investing more time and treasure in a commercial product I will likely make the components freely available for use as you've described. If that ends up being the direction I take I would certainly allow them to be used for the projects here at Boot-Land.

Regards,
...John

[John Hensley]

As a side note, I unpacked John's RescueBoot Setup which contains 3 things..

A windows .msi installer
A setup stub
A Windows XP imapi hotfix

I'm guessing the hotfix is for users with few or no xp updates, curious.

Because I'm still on an XP Sp3 system, I made an administrative install image on a local folder, which allows access to the program's files.
More later after an actual test..

The hotfix is for a bug I found in the XP IMAPI CD burning interface that prevents image files larger than about 150MB from being used when creating a bootable CD. I traced through the IMAPI.EXE service code and found the cause of the bug and provided Microsoft with a patch that they put into a hotfix for me. Unfortunately the hotfix they provided only supports SP1 and SP2 so RescueBoot still has to dynamically patch the code in IMAPI.EXE each time it burns a disc when running on XP with no service packs installed. Microsoft promised the fix would be incorporated into SP3 but I haven't verified this.

Regards,
...John

[TheHive]

During my test the hotfix was added to my test system.

Hope you stay around and decide to help in the Development and growth of future projects here.

[Brito]

At this time I'm still not sure what I should do with the technology. I'm currently giving RescueBoot licenses away for free to get feedback to use in deciding what direction to take going forward. If I decide that it's not worth investing more time and treasure in a commercial product I will likely make the components freely available for use as you've described. If that ends up being the direction I take I would certainly allow them to be used for the projects here at Boot-Land.

Thank you for taking in consideration my request.

Our talks around here give a good amount of focus on testing and exploring different options for boot disks - if you want feedback then this is a good place to discuss your project and see what other people think.

A XP/2000 write filter would be an excellent addon for us 'old' XP users.

[ktp]

The original error is probably documented earlier in the log file. If you would send me the log files I will take a look to see if we can get it working on your system. Here is a link to instructions for automatically generating a compressed set of the log files and then emailing them to our support email alias.

One quick question before you go to the trouble of sending the log files. Did you allow the setup program to reboot the computer before starting the RescueBoot Wizard? If not you will probably have problems running the Wizard until after you have rebooted the computer.

Thanks,
John Hensley
www.resqware.com

Hi John,
Yes I did reboot before running the wizard. I rerun the wizard and got same problem. Log file sent to you as instructed.

[John Hensley]

Most impressive project! I'll have to restore an old image to try it though, it doesn't install on builds higher than XP SP2 and I'm running XP SP3, now available as a beta release in a few languages.

Here is a link to a newer build of RescueBoot with support for XP SP3. I've only done preliminary testing on SP3 but hopefully it will work for those brave enough to try it.

John Hensley
www.resqware.com
Res-Q-Ware LLC
(Pronounced "Res-Cue-Ware")

[AeroXP]

Stop 0x7B when booting from cd. I have used the windows 2000 platform.

Normally this is caused by a read error when reading from the hard disk image on the CD during Windows boot. If you create an ISO image and burned it to the CD you should try imaging the CD to a second ISO image file and then comparing this file with the original to ensure its not corrupt.

We used to run into this problem frequently during testing but virtually eliminated the problem on CDs that RescueBoot burns on XP by generating an SHA-1 hash for the hard disk image file on the CD and verifying the integrity of the CD after it is burned so the user would not try to boot from a bad CD.

John Hensley
www.resqware.com

Windows 2000 Image is exact.(byte by byte)

So, Windows 2000 doesn't work at all.

[ktp]

Hi John,
Yes I did reboot before running the wizard. I rerun the wizard and got same problem. Log file sent to you as instructed.

Update :
I got John's answer. The new version (with XP SP3 support) mentioned above fixes my problem, and everything is OK now.
Thank John for your fast support.

[John Hensley]

Windows 2000 Image is exact.(byte by byte)
So, Windows 2000 doesn't work at all.

This is unusual because we have tested on hundreds of Win2K machines covering all available 2K service packs. If you would send a problem report with the logfiles attached as described at this link, I will see if there is something in the logs that will give us a hint as to what is causing your problem.

Two other things that would be helpful for me to know are, do you have any third party CD burning software installed on this machine that may have a driver installed and are you attempting to boot from an external USB or Firewire CD drive?

Thanks,
...John

[AeroXP]

Clean Windows 2000 Professional Sp4 Virtual Machine

No software installed. (excluding Res-Q-Ware)
-------------

Stop Error:

*** STOP 0x7B (0xF901F84C,0xC00000034)
INACCESSIBLE_BOOT_DEVICE

----------------

Log attached to post.
 Logs.zip   239.4KB   429 downloads

[John Hensley]

Clean Windows 2000 Professional Sp4 Virtual Machine
No software installed. (excluding Res-Q-Ware)
-------------
Stop Error:
*** STOP 0x7B (0xF901F84C,0xC00000034)
INACCESSIBLE_BOOT_DEVICE
----------------
Log attached to post.
 Logs.zip   239.4KB   429 downloads

Thanks for posting the log files. I think this line from the RescueBootImage.log could explain why you can't boot from the CD.

{ISO_REG }Total installed memory is 66572288 bytes so using 8388608 bytes for read cache, setting ReadCacheEntries to 16384 disk sectors

It appears that you are attempting to boot the RescueBoot CD on a virtual machine with only 64MB of memory. This is not enough memory to allow RecueBoot to create the virtual drive and still leave enough memory available for Windows to run in. As stated on the download page, RescueBoot requires a system with at least 128MB of memory.

If you change the virtual machine settings to give the virtual machine 128MB or more you might be able to boot the image you have created.

Thanks again for reporting the problem because it shows that I should should be checking for installed memory and warning the user before creating the image file.

Regards,
...John

[AeroXP]

Ok it works now.
------
Here's a picture:
 ResQBoot.bmp   1.37MB   695 downloads