bersem.blogg.se

1. SYMANTEC GHOST 8.3 NO CD
2. SYMANTEC GHOST 8.3 DRIVERS
3. SYMANTEC GHOST 8.3 PRO
4. SYMANTEC GHOST 8.3 SOFTWARE
5. SYMANTEC GHOST 8.3 WINDOWS

Some parts of the Phantom code, such as the ability to write to NTFS filesystems from MS-DOS, got folded into the main Ghost product. The Phantom project ran for about three years in parallel with the ongoing development of the Ghost code. The internal project name Phantom designated a complete rewrite of the Ghost cloning engine at Symantec in Auckland. However, a version of Ghost 8.0 was included on the Ghost 9 recovery disk to support existing Ghost customers. Ghost 9 continued to leverage the PowerQuest file format, meaning it wasn′t backward compatible with previous versions of Ghost.

SYMANTEC GHOST 8.3 WINDOWS

On August 2, 2004, Norton Ghost 9.0 was released as a new consumer version of Ghost, which was based on PowerQuest′s Drive Image version 7, and provided Live imaging of a Windows system. PowerQuestĪt the end of 2003, Symantec acquired its largest competitor, PowerQuest.

SYMANTEC GHOST 8.3 SOFTWARE

Technologies developed by 20/20 Software were integrated into Ghost after their acquisition by Symantec in April 2000. After the Symantec acquisition, a few functions (such as translation into other languages) were moved elsewhere, but the main development remained in Auckland until October 2009 at which time much was moved to India. I don't know of any switches to deal with that.Binary Research developed Ghost in Auckland, New Zealand. The -fni and -fnx switches do nothing, but those seem to remedy crashes with Ghost due to HDD access not boot media access. It all just falls apart when booting as well as running off the CD using virtual floppy or HDD emulation mode for boot. Remember, I can do this all day if the exact same boot info is initializing off of floppy and then running the executable off of the SAME CD. It does exactly the same thing, so this is leaving me to conclude that there is something going on specific to booting and running from the CD that Ghost doesn't like either because of the drive itself or the system.

SYMANTEC GHOST 8.3 NO CD

The interesting thing is I tried a boot disc from someone who built it with HDD emulation instead of floppy emulation, so no CD driver is involved. I've never known the Ghost executable to need the additional memory. Actually, I'm a DOS man from back in the day, so I'd thought about this. MENUITEM=B57, Broadcom NetXtreme - IBM T43 MENUITEM=RTSND, Realtek 8139 - E-Machine, HP NX9110, Compaq 1020v MENUITEM=DP83815, National Semiconductor DP83815 - HP NX9010 MENUITEM=B44, Broadcom 440x - HP 220, Dell D510

SYMANTEC GHOST 8.3 PRO

MENUITEM=E100B, Intel Pro 100 - EVO 300/310, IPAQ, PDSI Desk, Compaq EVO n610c,etc

I have pasted the contents of my autoexec and config below.ĮDIT: Just for the heck of it I tried the -fni switch to see if that would make any difference when booting from the CD, but it did not. In looking at similar topics about stack crashes they don't seem to apply to the way I'm doing this. It would seem that it has something to do with that driver not playing well with the CD, but I'm having trouble figuring it out. I am sure that it's not my executable because I can take the newly created CD and use that with my master floppy to get everything working again. I have tried setting the stack nice and high to no avail.

When I merged everything to a single CD, however, Ghost hangs on a stack overflow. With the new CD driver everything worked in test just fine. I've never had any problems with this.īefore merging everything to a CD I, as usual, did a test with my "master" floppy (actually just a floppy that has been imaged with my master floppy disc image) and a CD in the drive with the executable on it.

SYMANTEC GHOST 8.3 DRIVERS

My disk build process is the standard one of building all the boot files and drivers onto a floppy then using that as the boot image for Nero (or other) and adding the ghost executable to the disc in the disc dataspace. We just got in some Lenovo desktops that use SATA CD drives, and so I proceeded to make a new build of my disk with the gcdrom.sys file in place of the old oakcdrom.sys, which should have taken no time at all. I still keep all of the drivers on there "just in case." I have a good "universal" Ghost boot CD that I have been updating since Ghost 8.0, and when we went to 8.3 I added the Universal Packet Driver that largely negates the others.