-
GG1 I wasn't being literal when I said I was going to mess something up....I am a tweaker...I am not satisfied unless I am pushing the limits......I currently have an athlon 750 and my big athlon 1.2 and an old 120 mhz laptop that works awesome by the way with win95 on it.....and never to be satisfied I do want to add a few toys to my new machine but am already looking to build another one just for games and testing....I am looking at a socket 370 board that supports celeron 266 mhz all the way up to pIII 933 here is a link http://www.compgeeks.com/details.asp?invtid=728LMR
I have a celeron 333 chip that I would like to see how fast I can overclock it...and If if burn up this 41 dollar board big deal it will be all in the name of science right...just kidding...I am way to frugal to intentionally tear something up....but I may indeed pick this one up to play with...just add a cheap case and a decent video card and instant test and game machine
-
GG1,
Now I think I get it. You had the drive (still) on the motherboard controller, installed the drivers for the ultra card, then came down and switch the drive to the ultra card. After that the drive didn't work (when on ultra card).
Here's what the problem likely is. When you move that drive to the ultra card the drive geometry and/or translation methodolog being used changes. With the drive on the motherboard one set of values/methods is being used, and with it on the ultra card another set is being used. The net result: the data can't be read due to the different translation. To use the drive (now) on the card you are going to have to go back and set it up (re-partition and restore the data) with the drive on the card.
So, unfortunately, your gonna have to:
- With the drive on the MB controller, create a Ghost (you said you have that now) image of the drive (or at least that first 32 gig partition you set up).
- Move/connect the drive to the ultra card.
- Re-FDISK the drive (now you can use the full 40 gig as you wish, and partition it accordingly).
- Ghost the image created above back in to the (new) first partition on the drive.
PS. You did not install Maxblast (overlay) initially on that drive did ya? If so that would also be a problem when moving the card to the ultra card. The overlay would need to be removed.
------------------
Bookmark your post to make it easier to find.
And remember, please post back whether the problem is resolved or not.
[This message has been edited by DrMDJ (edited 09-26-2001).]
-
>> GG1 I wasn't being literal when I said I was going to mess something up....I am a tweaker...I am not satisfied unless I am pushing the limits...... <<
Well said, 'kaz. Some real pioneering and experimenting - all in the name of humankind...if a few components buy it in the process, well, that just underlines the dedication - call them martyrs if you will. Real science has it's price... https://discussions.virtualdr.com/
------------------
Karl, Denmark
---------
"..and may The Force be with you - too..."
-
hear hear, at long last, it's been put in concise form by our best friend..
https://discussions.virtualdr.com/
GG1, if you haven't done so
create two copies of the maxblast disk,
and two copies of a good booter floppy for your OS (to be)
(also create two systemised floppies with ghost.exe and mouse.com on it)
to test the booter floppy, boot from it
shut
also test the ghost floppy, by booting from it.
shut,
this procedure is to be used ONLY if you DO NOT have OVERLAY on older drive. That's because it would be skipped afterwards, with an invisible drive as result...
boot into BIOS setup
- select bootorder to A: > SCSI (or bootROM) > CDROM
- enable TRY other boot devices
- Refresh ESCD (update cofiguration data/aka force NVRAM update)
- save, and exit
it reboots
get in highpoint control panel by CTRL + H
select to use the connected drive as boot device (if more than one, you can even select which.)
reboot
boot from maxblast
prepare the new drive on highpoint.
(maxblast tells you which controllers it sees drives on)
go advanced option, fat32, more than one partition
partitioning and formatting will take all of five to seven minutes (mostly spent reading the screens)
it will ask for your system floppy.
because it also sees the old system disk, you are presented with an option to clone this drive over
(if you don't you won't be again offered the option without redoing the drive... but then again, at least YOU can use ghost. I have to write this for those without ghost as well, see) https://discussions.virtualdr.com/
so when it asks, you either go with it, or decline, and use ghost instead.
(and goose, if you start KNOWING you gonna use ghost, it would be wise to disconnect the older system drive, (IDE ribbon and power). you see, just ONE mistake, and your old drive gets wiped. Maxblast DOES tell you what type/which controller it finds the drive on. But mistakes happen... Murphy is alive and kicking. https://discussions.virtualdr.com/
personally, I would use ghost.
mouse.com will help ya.
once the older drive is ghosted over (you do partition to partition!!!!!)
you should be able to boot from new drive.
to test it, disconnect the older one (power and IDE)
if al runs well, leave it off, get it out, use it in BT at a later date
to do this while an overlay is present, you have to select bootorder so it boots from normal IDE controller, not SCSI.
------------------
[This message has been edited by jtdoom (edited 09-26-2001).]
-
Jaak,
Maybe I am just not understanding the issue(s). I focused on the fact that you listed two drives showing identical cylinder, head and sector count numbers (ie. 16383, 16, 63), yet with slightly different total sizes/capacities (ie. 40.0gb and 40.980 gb).
The point I was trying to make is that with the larger drives today (ie. anything over 8.4gb) the conventional method of using (and reporting) the cls/heads/secs as a measure of their size is out the window. Typical programs/utilities for reporting drive info will generally use bios int 13 calls to report this info. But that is misleading. Drives today aren't addressed as clys/heads/secs (logical geometry). So if one requests of display in this format a (essentially) made up set of numbers is shown.
When an int 13 call is used for any drive over 8.4 gig it will always return 16383, 16, 63. That's because that is what the "logical geometry" of the drive will always be (by convention). But the logical geometry is not the real physical size. The physical drive is really seen (and addressed) as a group of sectors (only). So, say, if a drive is 40.0 gb it would (in reality) be seen as 83220 sectors (each 512 bytes). But, in terms of trying to turn this in to the "traditional" cls/heads/secs display it would show as 16383/16/63. In fact, some software may show it as 1023/16/63. But in reality these numbers are meaningless.
------------------
Bookmark your post to make it easier to find.
And remember, please post back whether the problem is resolved or not.
[This message has been edited by DrMDJ (edited 09-26-2001).]
-
Good Morning All, Had to break off and get some sleep last night, but wow you guys really came up with some good stuff. Fascinating reading and as I thought on my part of it it appears to be configuration. Well, I'll study on it at work on breaks today.
I was partly kidding sarkazztic but the building would be interesting. Maybe think of it as being ...... https://discussions.virtualdr.com/ https://discussions.virtualdr.com/
Ah, Mosaic, mistress of the registry, you need to visit more often.
DrMDJ, read your thoughts over and after I figure out what you said exactly, I'll probably have a question or two or three. https://discussions.virtualdr.com/
Did Jaak say "concise"?
Kallikru, Are you sure you like being mixed up with this bunch? https://discussions.virtualdr.com/ https://discussions.virtualdr.com/ Just asking. It's off to work I go. Later
------------------
Seek knowledge and all else will follow
Please post back results - Press Ctl D to bookmark
Information
-
Hi all
DrMDj
have a fresh head and some cafeine in it.
at the moment I can recall having seen different drivesize reported by varying versions of fdisk, when ran on the same disk (that was way back)
when I encountered this, I had fdisked and formatted the disk on a working PC, and copied the cabs folder (with the version of windows this machine needed) to partition.
to my chagrin, I could start all over, because the drive was seen incorrectly by the booter for that version.
another instance of mismatching can happen when the BIOS needs the drive jumpered to use 15 heads rather than 16, and the drive was prepared on a conventional "16 head system".
this 15/16 issue should never happen with the highpoints.
DrMDj (once again) made a real good point about GG1's "limited to 32" drive.
GG1 told us he stayed without overlay.
still, with the highpoint having native support for the true size, I would clone the stuff while "32limited" is connected to MOBO connector.
"32" partition one to "40 on HPT" partition one, "32" partition 2 to "40 on HPT" partition 2.
(GOOSE, to do the cloning, you may very well have to boot from the OLD drive, and boot to DOS. ESPECCIALLY IF THERE WAS OVERLAY ON THE OLDER DRIVE.)
this means you have to set proper bootorder the way you need.
===================
onward...
[quote]You "should" have no problem putting the zip on the Promise Ultra66 if you choose too. In fact ya might as well. While some DVD drives will use ATA66, in general DVD, cd, cdrw and zip drives are only capable of ATA33 at best. So one is best offloading non-ate100 devices and reserving the MB controllers for devices that can actually benefit from ate100.[/qoute]
yep.
I never saw performance issues when zip was connected to ata 66 onboard.
I have ONE consideration regarding CDROM/DVD/CDR/RW
to boot from cdrom, when it's on a true scsi, you can easily do so, and a start floppy will see it (no sweat)
when its on a highpoint, hmmm, the start floppy don't find your CDROM.
you "may" be able to boot directly from it, tho, I did not try that.
anyway, the readme on highpoint 370 tells you it is better to not connect cdrom/atapi devices to it.
just the one issue (no cdrom support when using floppy start disk) is enough to heed the warning.
when I tried it today, ME floppy didn't find cdrom, and neither did an 98SE floppy.
------------------
Kind regards, Jaak
[This message has been edited by jtdoom (edited 09-26-2001).]
-
Hmmm.. started to read the first thread, takes some time to catch up..
What parts did you go for?
//Jens
-
and more important, is everything working out fine?
-
Hi klemming, All the components have not come in yet. The In Win S500 case, WD 40GB HDs (2), and RAM are in. The ASUS A7V MOBO, 1.1Ghz AMD Tbird, fan are on the way. Have to pick up a sound card. Operating system will be WIN 98SE. 17" monitor.
Budget = $1000.00 or less.
Had a HD failure and we've been working on it and the subsquent upgrading and whatever else people wanted to know about. Replaced the CDROM, the HD (WD 40 GB HD) and even though the one drive that is over 32GB is detected, it cannot be used because of the 32GB barrier. So got a Maxtor Ultra ATA 100 PCI card and the drivers are installed but it's not picking up the HD at all. That was short and I hope enough is there for you.
BTW, the PC being worked on is a Compaq 5360.
------------------
Seek knowledge and all else will follow
Please post back results - Press Ctl D to bookmark
Information
-
Here goes machine number 2 this month...I just ordered this board http://www.compgeeks.com/details.asp?invtId=728LMR
I have a celeron 333 or 366 I will have to look and see what it is...I have tested it a while back so I know it is good.....I also ordered a 32mb savage 4 video card...and a low end atx case....this is just for gaming for now....later I will order either the celeron 700 or the pIII 933 and max the board out if I decide to keep it....will be selling the slot A 750 system that I built for myself earlier this year.Keep your fingers crossed that the wife doesnt do me bodily harm for playing musical computers...everytime she gets comfy with one I put together another one...and say here honey try this one out....UPDATE...the Athlon 1.2 is still running at 1.332 ghz no problems with heat or instability in win2k and am testing under 98se but I do not anticipate any problems there either with the exception of the occasional b.s.o.d that I am sure I will run into sooner or later...
[This message has been edited by sarrkazztic (edited 09-26-2001).]
-
The power of suggestion. Need I say more? https://discussions.virtualdr.com/ https://discussions.virtualdr.com/
------------------
Seek knowledge and all else will follow
Please post back results - Press Ctl D to bookmark
Information
-
Hmmm - I had just finished writing this piece and as I clicked "submit" the beast BSODed on me - some kind of driver failure. And that after 2 weeks of continuous, flawless operation (W2K). The thing automatically rebooted before I could read the whole BSOD message or write anything down. The eventlog says:
"The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xa2010a74, 0x00000000, 0xbb3ca55e, 0x00000002). " Not much to work with here.
Anyway...
gg1,
Sure, I like being mixed up with this bunch.
a) They are really nice people with my own sense of humor - and a touch of sarcasm, love it...
b) They love computers and they love talking about them.
c) They know a l o t about computers so there's a lot to be learned here. And one's never too old to learn some new tricks, right..?
For 13 years I've made money in the programming business (PL/1 & DL/1 - lately C and SQL - still a beginner..) and for 20 years I've worked with computers (C64, Amigas and PCs). I've spend a lot of my spare time during the last 5-6 years building, repairing and modifying PCs for myself and others.
I'm currently running my own little computer-farm and keeping computers running for 6-7 other "computer-illiterates". VDr sure is the right place under those circumstances...
d) This is a good place to expand my english knowledge, particularly in the technical field. It sure helps to have an engineering background, but there are things you just can't find in any dictionary.. https://discussions.virtualdr.com/
Right now I'm getting ready to cut up a ribbon cable as I mentioned soem time ago. I've decided to start with a 50 pin SCSI ribbon to get some practise. An ATA66/100 looks like a real challenge that will need a steady hand, hence the practise. Besides, SCSI cable do take up a lot of space and disturb the airflow.
It seems my posting regarding my the unfortunate killing of an (factory-flawed, it seems) 18 GB SCSI LVD2 drive was lost in a "thread disaster". The drive sent off small fumes and went completely dead the first time I put power to it. Definitely smelled like burned insolation.
Well, I've now received word from the dealer that they have tested the drive and found it to be dead (hmmm - thought I told them that..? https://discussions.virtualdr.com/ ) and that a free replacement is being sought and sent as soon as they can find one - they'd better...
------------------
Karl, Denmark
---------
"..and may The Force be with you - too..."
-
Now I did the wd harddrive and card like GG1 did and it worked for me https://discussions.virtualdr.com/
Only difference was I did a clean install of SE while he used the Restore cd which seems to have the Bomide on the cd.
Will ghost pick up the nonDOS info and move it. Compaq ID on the Harddrive is what I am refering to. Or another program?
Seems I heard leave it [the compaq]alone for now!
So, it is back on the original harddrive. https://discussions.virtualdr.com/
But , time will tell https://discussions.virtualdr.com/
------------------
SMILE
and post back
[ Book mark this post to find it again]
[This message has been edited by Train (edited 09-26-2001).]
-
Hi All, Checking in. Good post Train, the answer ought to tell us something 'cause I sure don't know and still assimilating what has been written so far. What I need is the proper procedure as I have never done this before.
Kallikru, I wish you had not mentioned the great people here. It will give them the "big heads" and they will be hard to live with. https://discussions.virtualdr.com/ https://discussions.virtualdr.com/ LOLROTF
------------------
Seek knowledge and all else will follow
Please post back results - Press Ctl D to bookmark
Information
