problem with installation

[Christian Mueller]

I have a problem with the installation of Windows 95 and 98: The system
gives me the message that there is a cab-file which cannot be open. There is
nothing on drive c:. I made a format c:. Does anybody know what I can do???
Greetings
Chris

[WinFiddler]

THe CAB file is on your windows CD. Borrow somebody elses and put your
number in.

--
WinFiddler
www.file-replacement.com
ICQ 77746157
Christian Mueller <c.mu...@addcom.de> wrote in message
news:8ksbqt$5ma$1...@riker.addcom.de...

[Todd Weiss]

is this and amd system with a via chipset? if so, disable your cache in the
bios. there are some instances in which the processors are actually to fast
to decode the cab files. we saw it often with 98 when it first came out and
I supported it for ms
"WinFiddler" <mat...@file-exchange.fsnet.co.uk> wrote in message
news:#16zD#27$GA.281@cppssbbsa04...

[mossy]

yes i had the same problem till i formatted it 3 times,then it came
right,it used to say there was a cab file missing or the CD was
corrupt,or the hard drive was buggered.wash the CD in warm soapy
water,that way it can be read ok

[Excel Career College]

On Fri, 21 Jul 2000 14:52:44 +1200, mossy <mo...@es.co.nz> wrote:

>yes i had the same problem till i formatted it 3 times,then it came
>right,it used to say there was a cab file missing or the CD was
>corrupt,or the hard drive was buggered.wash the CD in warm soapy
>water,that way it can be read ok
>

With rsespect to the WUSIN errors, I have successfully overcome them
ass follows :
IF you have a lot of room , copy all of the windows files to the hard
drive ... ... and install from the hard drive ... I can't recall which
CHIPSET causes this problem, but the problem is with the onbaoard IDE
(built in IDE controller ) ont he motherboard .... also .. W.R.T
the problem of FDISK /mbr ... ... years ago I wrote a rpogram using
int 13 for my wifke's private school to grab the boot sectors of the
primary drive ... I found out that EACH drive (even thought the same
make and type) will have differnct boot sectors. My solution to boot
sectors virusi is to rewrite the boot sectors from a know good file
and the to reboot the system before the virus gets a chance to writei
itself back ... for whats it si worths, none of the 80 computers has
ever suffered from a successful virus spred... thsi is what you ddo
in assemblems(or call to assembelr code)

set the drive register to look for drive 0,
find out how many sectors per track on that physical units .. ie
we'll call it SPT
start reading at sector 0 and read SPT + 1 sectors and write the
informators to a file (preferable on a floppy drive) ... to reverse
the procedured, set the int 13 call to write (as opposed to read) and
that will write the infor back to the hard drive ... BOOT sector virus
are simply NOT a problem ...

if you have to wipe aout a hard drive, to prepare if for FDISK ,,, you
can do this

create a script file (text file) called AIEE.txt .. any other name
will do ... preferredbly one signifying DEATH is approrpriate
make the text fiel read as follwos :
a
mov ax,330
mov cx,1
mov dx,80
mov bx,3000
mov ex,bx

int 13
int 3

g=100
q

save the above ... when you want to wipe out your hard drive
run the program debug .com (or is debug.exe) as follows
debug < aiee.txt

NOW YOU VILL BE READY FOR FDISK LIKE NEVER BRFORE