mikeyb
-
Content Count
9 -
Joined
-
Last visited
Content Type
Profiles
Forums
Calendar
Posts posted by mikeyb
-
-
on some of the dels you have to put the largest mem module in slot 1. I have found this on a few del dimensions
mikeyb
-
usually the master is the drive that is 'source' and the slave is the 'destination' device. there will be no speed increase, however the speed of the burn depends on a few things.. mainly everything runs at the slowest speed of any of the devices
This could be the DVD reader in 'master'
the DVD writer in 'slave'
the setting on your buring software X2 X4 X8 X16 etc
the media you are buring onto DVD/rw media with X2 burn
so for instace...
you have a DVD reader which can read the disk at x16, but your writer only writes at x8 speed, then the transfer will be at 8speed
if you then are using blank dvd's that are x4 speed, then the burn will be x4..
I hope you get the idea? - it will only burn as fast as the slowest setting\device\media.
regards
mikeyb
-
could you tell me when it locks up what processes are running on the machine that locks? a list of services, and Virtual Machine sessions on that PC? and does it lock up randomly or when you are performing a specific task.. i.e emailing, printing, file saving, antivirus updates or scans?
mikeyb
-
Hi jimras,
you may want to try booting to a DOS prompt and running a CHKDSK /F on the drive, as long as the BIOS is detecting the drive that is! see if it finds any problems on the drive.
mikeyb
-
hello,
just adding another suggestion
you could always backup by creating an image of your machine, not only do you get the 'data' you also get a whole image of the machine, this could be put on a CD using something like nortons Ghost.
when backing data onto external drives there is always the posibility of missing some data.. IE favorites for instance, an image would get everything, keep a cycle of 4 images over a period of a month that way if there is a problem then you can go back 3 weeks if needed.
mikeyb
-
hi,
yes you can but if you are using Nero, then when you get to the stage where it says burning at 52X - change the setting in the drop down to the speed of the media.. 16X for instance otherwise the burn will start and it will fail with buffer overruns.
mikeyb
-
Hi there,
I have worked on these monitors before, and have also come across the problem you mentioned, the reason is in reference to your resolution settings, the screen tries to adjust to the best position based on the selections in the display properties, however you should be able to override the monitors 'auto' settings by turning on the OSD lock. (setting on the front of the screen menu buttons) in the same menu as you would change the screen settings in the 1st place.
hope this helps.
mikeyb
-
Hi there,
I would just like to add my 2 cents. Has this machine EVER booted without the error? you say it is a second hand machine, maybe the battery is not on the motherboard and it was sold without one!
this would explain the fact that you cannot see the battery! try looking for a plastic bit on the motherboard
This is an image of the disc battery holder, you will see how the battery clips into place and it sits in usually a black plastic bit that rises slightly from the surface of the mobo
the second image is of what a battery looks like whn it is out of the mobo housing.
some older batteries are in a barrel shape similar to this image (taken from an amiga)
or this one.. battery on the right of picture.
hope this help
mikeyb
137 Gb Limit
in Windows 10, 8, 7, Vista, and XP
Posted
Hi there,
regarding MAX HDD limits,
The limits imposed by the Hard Disk Drive Interface
The Hard Disk Drive in the first IBM PC/XT Computer had 306 Tracks (Cylinders), four (4) Heads reading four surfaces on two platters, and used 17 Sectors per track. 306 x 17 x 4 x 512 Bytes per Sector gave a capacity of 10,370 KBytes.
However on the newer IDE Hard Disk Drive Interface, and the universal device interface, SCSI, do not need to know about the numbers of Heads and Cylinders, as they are designed quite differently. They are only concerned with the total number of Sectors on the Hard Disk Drive.
Limits imposed by the BIOS
The BIOS (Basic Input Output Services) provides disk services via a software interrupt service routine, Int 13 hex.. These services were originally designed for Floppy Disk Drives, and this is the cause of many of the limits. Three eight bit registers are used to store the Track, Head and Sector detail. The CH is used to store the Track number, the DH register stores the Head number and the CL register is used to store the Sector number. Eight binary bits can represent 256 values, so this means this BIOS service routine can support up to 256 Tracks, 256 Heads, and 256 Sectors per track. The above organisation would give a capacity of over 8 GByte, not a bad insight for 1982, when Hard Disk Drives small enough to fit inside a PC Computer were just becoming a reality. The only problem was the arrangement was wrong, a Drive with more than 16 heads is impractical and even the first Hard Disk Drives had more than 256 cylinders.
This BIOS imposed limitation was overcome by modifying the Int 13 routine for Hard Disk Drives. The use of the CL and CH registers was changed. The low six bits of the CL register stored the number of sectors and the extra two bits not used in CL were tacked onto the front of the 8 bits in the CH register to give 10 bits for the number of cylinders. This means the Int 13 routine, when working with Hard Disk Drives, could recognise a maximum of 1023 Tracks, a maximum of 63 Sectors per track, and a maximum of 256 Heads (sides). The 1023 Track barrier is a problem as modern drives can have as many as 5000 Cylinders.
One way to overcome the problem is to not tell DOS the drives real configuration. Rather than saying there are 2000 Cylinders and four Heads, we say they have 1000 Cylinders and eight Heads. The resulting capacity is the same, and the process is called TRANSLATION. Remember we are using the terms Cylinder and Track almost interchangeably here, a Track is a single track on one side of a platter, a Cylinder refers to all the Tracks on one plane.
The last layer in the path between the disk and the user is the Operating System and DOS and Windows have their own size limitations. The major limitation here is caused by the Boot Record. The boot record is located in the first sector of track one on a Hard Disk Drive and contains a record of the disks format and a short boot strap loader routine. DOS versions up to 3.31 set aside two bytes (16 bits) for a record of the total number of sectors per logical drive. Under these earlier DOS versions, a large drive could be split into a number of logical drives by the FDISK command (each must be 32 MByte or less) and this made it possible to use drives larger than 32 MByte with these DOS versions.
The 16 bit limit on the total number of sectors meant a Hard Disk Drive could have a maximum of 65,536 sectors, a total capacity of 32 MByte. (65536 sectors x 512 bytes per sector) DOS 3.1 and later removed this limit by setting aside four bytes for the total number of sectors and the 32 bit number produced can describe a two Tera Byte disk size.
Here is a table describing where the original IDE specifications 528 MByte limit came from. The maximum capacity limits of IDE Hard Disk Drives was the combination of the lowest values for each parameter across the four layers of communication.
the next 3 lists show the following...Limit imposed by the Int13 routine...Limits imposed by the IDE interface...Limit on the original IDE specification
Maximum sectors per track 63 255 63
Maximum number of heads 255 16 16
Maximum number of cylinders 1024 65536 1024
Maximum capacity 8.4GB 136.9GB 528MB
You are also correct regarding OS's that will have a limit as well, for instance you cannot stick a 120GB drive onto a win98 machine as it is running a FAT32 partition, however, there are ways around this, download the maxblast 3 software and it bypasses hard drive limitations. well i think i waffled on enough.. and I hope this was not too boring for you
good luck with the drive.
Mikeyb