Sign in with
Sign up | Sign in
Your question

Help!!! problem!!

Last response: in CPUs
December 30, 2001 11:12:12 PM

(sorry dont really know where it should go)
Guys I have a problem when I try to install a game it says " not found Please insert disc 0 now" Well there is no other disc. Do you know what this is? I have the problem on 2 computers. All diff games and they work on other comps fine. Please help!

1.1 tbird
gf 2 mx400
640 pc133

other one is:
athlon 1600xp
voodoo 3
256 ddr

If you need more info please tell me! And thank you!

More about : data3 cab problem

December 31, 2001 4:39:44 AM

shouldn't have anything do do w/ your hardware...the only thing i can think of is that you may have "borrowed" this program and may need to re "borrow" it. or whoever burned it (the licensed company of course) may have not included the file.

no vestige of a beginning, no prospect of an end, when we all disintegrate, it'll all happen again.
December 31, 2001 3:21:25 PM

nope its the real deal...and it works on the comp across the hall so 2 out of 4 comps run it and the other 2 dont...i dont understand...thx tho
Related resources
December 31, 2001 3:52:19 PM

here's a hint.

when something weird happens on one computer but not on others that means there is software curruption. What causes software curruption? :)  a virus can cause that.

another possibility could be that your hardware (cd-rom is likely) is bad.

go the cheaper route and buy yourself an antivirus program. If you don't have one already. Don't install it right away. Although you could and should if you have any important data on it, otherwise delete everything on that computer and start from scratch. fdisk and delete all partitions and then do a c:\fdisk /mbr to format the master boot record. I'll bet it's a nasty virus. If not, then the next likely cause would be the cd-rom is dead. try different cd's too and see if the same problem occures.

good luck!

<A HREF="" target="_new"> My Rig </A>
December 31, 2001 4:02:34 PM

is that particular file on the disk though? or is it something it's looking for in the operating system?

no vestige of a beginning, no prospect of an end, when we all disintegrate, it'll all happen again.
December 31, 2001 4:37:52 PM

Copy the installation to the hard drive and try again.

Also search your CD/HD for that file so you know where it exists and point the install at it when it fails. If that doesnt work, copy the cab file to the HD and point install at the copy.
December 31, 2001 4:43:14 PM

well ok heres the deal it does that with all wont load used too, i reformatted awhile back and before that it was working but doesnt seem it might be that...but yea and the other comp is brand new...and it does the same im not really sure...i think the drive should still be good...but idk...i think i will reformat and try it on one of them...but im not really sure that will fix it...
December 31, 2001 4:48:15 PM

and is that c:/fdisk \mbr anything special or hard? i have reformatted it before but never done that
December 31, 2001 4:54:26 PM

It might, MBR stands for "master boot record" it will erase the old MBR.

If you fdisk you will lose your data.

Also is the CDROM drive old? maybe its haveing a problem with the format on the CD.
December 31, 2001 5:00:38 PM

it just formats the MBR. windows does that everytime you install it. Just a good idea to do that to rid whatever virus that could be lurking in the MBR. Or whatever curruption. Not needed really, but there if you can't install windows because of a virus. A virus could make it's own partition in the MBR and hide there and then lurk down and curpt whatever data files it feels like. fdisk /mbr i believe deletes the partition and formats it.

I should look that up just to be sure.

<A HREF="" target="_new"> My Rig </A>
December 31, 2001 5:05:26 PM

here ya go.

The MS-DOS Fdisk utility usually updates the master boot record (MBR) only if no master boot record exists. Repartitioning with Fdisk does not rewrite this information.

Fdisk has an undocumented parameter called /mbr that causes it to write the master boot record to the hard disk without altering the partition table information.

WARNING : Writing the master boot record to the hard disk in this manner can make certain hard disks partitioned with SpeedStor unusable. It can also cause problems for some dual-boot programs and disks with more than four partitions.


What is the MBR?
At the end of the ROM BIOS bootstrap routine, the BIOS reads and executes the first physical sector of the first floppy or hard disk on the system. This first sector of the hard disk is called the master boot record (or sometimes the partition table or master boot block). There is a small program at the beginning of this sector of the hard disk. The partition information, or partition table, is stored at the end of this sector. This program uses the partition information to determine which partition is bootable (usually the first primary DOS partition) and attempts to boot from it.

This program is written to the disk by the fdisk /mbr command and is usually called the master boot record. During typical operation, Fdisk writes this program to the disk only if there is no master boot record.

NOTE : The fdisk /mbr command only re-writes the MBR on the system drive (DISK-0) using BIOS calls. You cannot specify any other drive for the fdisk /mbr command to operate on other than DISK-0.
Why is the MBR Changed During Setup?
During the installation of Microsoft MS-DOS Upgrade, Setup replaces the master boot record on the hard disk with code to display a message similar to:
The MS-DOS 5.0 Setup was not completed.
Insert the UNINSTALL #1 diskette in drive A.
Press the ENTER key to continue.
This message should be erased and the master boot code rewritten before Setup is completed. If a problem occurs during Setup and you return to the previous version of MS-DOS, Uninstal should also remove this message. However, if Setup or Uninstal does not remove this message, or if the master boot record becomes corrupted, a new master boot record can be written to the disk using the following command:
fdisk /mbr
Do not use this command if any of the following conditions exists:
The disk was partitioned using the Storage Dimensions SpeedStor utility with its /bootall option.

More than four partitions exist.

Certain dual-boot programs are in use.

The Storage Dimensions SpeedStor utility with the /bootall option redefines the drive's physical parameters (cylinder, head, and sector). The /bootall switch stores information about how the drive has been changed in an area of the master boot record that MS-DOS does not use. The fdisk /mbr command erases that information, making the disk unusable.

Some older original equipment manufacturer (OEM) versions of MS-DOS and some third-party partitioning utilities can create more than four partitions. Additional partition information is commonly stored information on partitions in an area that the fdisk /mbr command overwrites.

Some dual-boot programs have a special MBR that asks you at startup which operating system you want to use. The fdisk /mbr command erases this program. Dual-boot systems that boot whichever partition is marked Active are not affected by the fdisk /mbr command.

For more information about partitioning, query on the following word in the Microsoft Knowledge Base:
The third-party products discussed in this article are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.

More information on partitioning, disk organization, and the boot sequence can also be found in Chapters 3 and 8 of the DOS Programmer's Reference by Terry Dettmann, published by the QUE Corporation; Chapters 2 and 10 of Advanced MS-DOS Programming by Ray Duncan, and article 3 of The MS-DOS Encyclopedia , both published by Microsoft Press. ";EN-US;Q69013

<A HREF="" target="_new"> My Rig </A>
December 31, 2001 5:10:20 PM

here, explains in full.

"you also need to understand something about the typical disk layout of these structures.

Since DOS 3.0 the DOS boot sector has conventionally started at the first sector of a track (often 1,0,1, but never count on it). This has meant that all of the first physical track except the MBR (first sector) is "wasted space."

Now, on to what FDISK/MBR does...

Normally it overwrites what would be the DOS pre-bootstrap code part of the MBR, leaving the partition table and signature mentioned earlier.

Generally though, it sounds fairly harmless, right? "Generally" it is, and that explains why on many, many machines thousands of people have ignorantly done no damage to their drives.

The problem is, there are an awful lot of machines where my earlier description of the MBR contents and the layout of things on the first track of the hard drive do not match what FDISK is programmed to assume, and, as an Information Technology professional, I cannot conscientiously recommend something that can trash someone's disk without giving them a clear understanding of the possibility of making matters worse. This is why I refuse to post submissions that basically just say "Try FDISK/MBR" in response to "How do I clean <some boot virus>?" questions.

Examples of things that can go wrong and what happens:

A security system that does on-the-fly encryption and decryption of the hard drive may be installed with a pre-OS "driver" loading from the MBR bootstrap code. Such a scheme, being non-standard, has its own special MBR bootstrap code. Such code is typically much more than one sector (512 bytes) and as there is no DOS to interpret the file system, the "driver" is usually stored in the "wasted space" on track one (after the MBR) I referred to earlier. (A dual-boot MBR, e.g., OS/2, is another example that might fit into this category.)

You will lose access to your drive, at least until appropriate actions can be taken to reinstall the encryption software. Well-designed software of this kind will have been designed with data-integrity as well as security in mind so should have install options to allow reinstalling over a "corrupted" setup. Once FDISK/MBR has been run, the hard drive will most likely be completely inaccessible (after all, this is the point of most disk encryption schemes). Given someone was ignorant enough to corrupt it in the first place, what do you reckon the chances are they will have any idea they had a disk encryption scheme in the first place? (Or, at least, what are the chances they know how to have the installation fixed?)

A virus that does not preserve the original partition table in the right place or that encrypts it.

How many people do we get here [posted in the newsgroup comp.virus] per year with horror stories of "losing their C: drive" after FDISK/MBR against a Monkey-infected drive (or several other quite common viruses that also do not preserve the MBR in place)? These are usually quite easily fixed once someone who really knows what they are doing gets involved (unless the "expert" who just trashed the disk insists on continuing...).

A pre-OS driver to support "large drives" has been installed so a drive greater than 528MB can be used in a machine with an "old" BIOS. The mechanism for this is much the same as in 1 above.

Such large disk drivers (which are effectively a software BIOS extension) are quite common. (Anyone with a machine more than about 18 months old who has "upgraded" their hard drive is likely running one.) FDISK/MBR removes the driver that correctly allows access to cylinders 1024+, but the effect of removing it varies depending on all kinds of variables to do with the machines BIOS, the way the drive was partitioned, etc. As with encryption systems, many users of such large disk drivers have no idea that they are running one--after all, computers are just "tools", you don't have to understand how they work to use them. Because the driver load mechanism is similar to the security products mentioned in 1, similar comments apply about fixing these should they be damaged by an unwanted FDISK/MBR.

A virus that leaves the partition table in place, but stores critical viral variables in what is normally the bootstrap code portion of the MBR. A particularly nasty possibility here is that a virus may be running on-the-fly encryption/decryption of the drive's contents using an encryption key that was randomly generated at infection time.

At least one family of "in the wild" viruses, One_Half, does what I described here. FDISK/MBR against a drive infected with a One_Half variant (or any future/unknown virus that uses a similar "trick") will remove the MBR infection (One_Half is multi-partite, so it doesn't necessarily clean One_Half completely), but leaves you with a hard drive whose contents are partially encrypted with a now unknown and irretrievable key. This is definitely a case of the "cure" being worse than the disease!

Some antivirus (or general "system integrity") software may have loaded a special MBR to allow itself to check for possible MBR infection/change attempts.

FDISK/MBR against such integrity systems has a wide range of effects depending on the design of the system, from simply warning you of a change to the MBR to completely locking you out of your hard drive until the system is reinstalled/reconfigured.

A currently unimplemented virus attack I will not describe in detail here.

I know of a boot virus attack that has only been partially implemented in a real world virus to date, where FDISK/MBR would apparently clean the virus, but on rebooting from the hard drive, the virus would be able to reinstall itself and would "know" that a (clumsy) disinfection attempt had been made against it. If the virus' author was so inclined, this could be used as a trigger for some nasty payload (like reformatting your drive).

I could have named examples of the first five, though the risk in doing that is people who do not know better will think they are the only possibilities, rule them out and blunder on.

Just in case it is not clear at this point, all of these things replace (part of) the "normal" bootstrap code in the MBR with their own code and/or data and in some way critically modify the function of the bootstrap process.

Now you understand why FDISK/MBR is DANGEROUS!

<End quote>

Bottom line:

Don't Use FDISK /MBR!"

<A HREF="" target="_new"> My Rig </A>
December 31, 2001 9:11:19 PM

ok...but i dont think it is a virus because i have norton and it does it on this brand new computer that couldnt have been exposed to a virus already...i dont see how...but i think i will just reformat...
January 1, 2002 6:47:37 PM

aright i tried to copy the disc to the hard drive and it came up with an error with all the programs on both i am not all that familar with that /mbr and im not sure i should do that cuz it sounds like you can really mess up your it hard? can i find instructions somewhere? cuz i really dont want to mess up this brand new comp...thanks guys
January 1, 2002 6:57:49 PM

yea and this might sound stupid (ok it DOES sound stupid =P ) but after the reformat i didnt install drivers or software for my cdrom...should i? and i really dont know what type of cdrom it is it just says toshiba xm-6702B so do i need drivers for it? and then i just noticed this disc detector that a problem? thanks for your help guys
January 2, 2002 7:21:13 AM

Unless you are running DOS, there should be no reason to install drivers for your CD drive. Put a CD in the drive, if it works don't worry about it. As to your problem, it sounds like an installation error. What program are you trying to install/run, on what operation system, and does the program use multiple disks?

January 2, 2002 5:27:12 PM

"i dont think it is a virus because i have Norton"

hehe if you think you are safe cause you have Norton you fooling yourself. Think about it, Norton is the most popular virus scanner and most virus writers write virus to defeat the scanner.

I'd get f-prot it is allot "smarter".
<A HREF="" target="_new">;/A>

a b à CPUs
January 2, 2002 10:03:28 PM

sounds like the cd is damaged. some cd-roms are better at reading slightly damaged discs than others, which would explain why it works on some computers not others. had a similar problem with pagemaker. could see the damage on the disk and would always miss one file on install. after installing/uninstalling a million times it finally worked but it wasn't worth the effort and i think i was just lucky.

i had a drink the other day... opinions were like kittens i was givin' away
July 5, 2011 10:07:06 AM

Yep had same prob here, with MOH PA *.cab files. My discs where well used and thought it was a possibility it was a win7 x64 prob (still not sure, due to the condition of these discs)

Tryed a portable USB-DVD, install with full admin privileges drive they are more rugged and flexable like laptop disc drives.

Install finished by copying,, etc to the desktop pointed installation to the desktop when it required the particular file and it continued.

The copying of the files took different amounts of time to copy even tho these *.cab files are around the same size, strange or disc surface damage?

Possible safedisc/win7 x64 prob?

Going to try different patches and *.EXEs/No-CDs due to cd/dvd drive not recognising those *.cab files that are there and can be copyed to the desktop.

*.EXEs/No-CDs from and in different compatibility modes with admin privileges.

Seeing I paid for this game (years ago) I feel entitled to use it. The patches are finishing.

Wish me luck

July 5, 2011 11:51:11 AM

Hi Back again, installed the patches did 1.0_1.2 last. Did process of elimination for naught with a few near BSOD.

Got file from game copy world Tryeddev-mpp2.rar from under MOH: Pacific Assault v1.2 [MULTI] No-CD/Fixed EXE. Replaced the mohpa.exe with original and Allah kazzam! it works on win7 x64 but no sound so far

Gonna do some research for the sound it's a miles sound system driver(s) I now need.
Haven t seen them around for a few games from dos like terminal velocity and duke3d if my memories hasn't failed. :( 

a c 141 à CPUs
July 5, 2011 11:05:26 PM

Mmmm 10 year old goodness, like aged scotch!
a c 190 à CPUs
July 6, 2011 12:38:50 AM

Please dont necro ancient threads, im closing this now.