»

[mike-]

I have some issues.

Firstly, i cant handle files above 32 or 16 megs, this could make sense as i have 32 megs of ram, but i cant wget above 32 megs nor ftp, and i cant archive with tar above 32, but i with lha, 16 seem to be the limit.

My second issue is with the hard drive, it refuses to see more then 8 gigs of the 60 in there, this wasnt a problem before with 3.1 but im now using bb2 i figure re-defining the drive might work but that brings me back to my first issue, as i need to back things up.. Anyone got a take on this?

Its worth noting that im using blizkick with speedyide and speedychip and a few others.

[darksun9210]

i'm not really unerstanding whats going on with the archiving issue, surely if you unarchive from a file on disk to a directory on disk, or the otherway round, you shouldn't have a problem as it should only use the memory it needs, rather than having to load the whole archive into ram?

i'm with you with the hard disk problem though.
i've got a 40Gb drive in my A4000, 3.1 roms, installed 3.1, upgraded to 3.5, found my 3.9CD, upgraded to 3.9, boing bagged it with both 1 and 2. and i'm still only seeing 8Gb of the disk.
at the moment configured partitions with 1Gb system disk, 1Gb mac partition, 2Gb apps, 4Gb data...
fix disk size tells me the drive geometry is confugured properly, and i'm running SFS not FFS ... so a little puzzeled.

one of my A1200's is the same. i have had it working fine before, as i've had it's 60Gb drive setup with 1Gb system, 1Gb mac, 2Gb temp, 25Gb apps, 25Gb data. but after geting annoyed with the warpOS/warp3D issues, blew the whole lot away and started again, i can't get more than 8Gb. and fixdisksize tells me its fine...? again, 3.1 install, 3.5 upgrade, 3.9 upgrade, not been boingbagged yet...

[mike-]

About the same setup here,tho i've tricked around with wb3.1 to have it basically become 3.9 without all the fuss. this all started when i fired up toolbox3.9 and nuked my drive

[darksun9210]

when i had an A4000 and 3.5 had just been released, and installed, i found out the hard way to NEVER user the 3.5 version of HDtoolbox. that was just asking for trouble. i'd always leave the 3.1 version on there...

[mike-]

Yeah i have that copied to a folder here, i'll be using that once i get this file handling issue sorted, i think theres one on aminet too tho

[mike-]

The file problem seems to be blizkick :\

[Thomas]

Firstly, i cant handle files above 32 or 16 megs, this could make sense as i have 32 megs of ram, but i cant wget above 32 megs nor ftp, and i cant archive with tar above 32, but i with lha, 16 seem to be the limit.

Check MaxTransfer for all your partitions. If it's higher than 0xffffff set it to 0xffffff.

Check number of buffers for all your partitions. Use 50 buffers per GB, but not more than 300 or so. Note that each buffer is as big as the block size defined for that partition.

Add more RAM.

My second issue is with the hard drive, it refuses to see more then 8 gigs of the 60 in there, this wasnt a problem before with 3.1 but im now using bb2 i figure re-defining the drive might work but that brings me back to my first issue, as i need to back things up.. Anyone got a take on this?

http://aminet.net/package/disk/misc/fixhddsize

Bye,
Thomas

[mike-]

Thanks, just as i crossed blizkick off the list of suspects =)

[AmigaMance]

Firstly, i cant handle files above 32 or 16 megs, this could make sense as i have 32 megs of ram, but i cant wget above 32 megs nor ftp

No, it doesn't make sense, unless you are trying to download the files to the Ram disk or unless wget has a bug. (I don't think i have ever used it)

i cant archive with tar above 32, but i with lha, 16 seem to be the limit.

Tar is probably memory hungry. I don't think that you should encounter such problem with lha, but i'm not so sure.

My second issue is with the hard drive, it refuses to see more then 8 gigs of the 60 in there, this wasnt a problem before with 3.1 but im now using bb2 i figure re-defining the drive might work but that brings me back to my first issue, as i need to back things up.. Anyone got a take on this?

Is this problem solved with Thomas's utility or it persists?
Note that HDInstTools has a small issue with setting partitions bigger than 8GB, but since you are using HDToolBox..

Its worth noting that im using blizkick with speedyide and speedychip and a few others.

What is your CPU, IDE interface, File system, scsi.device version?

[mike-]

Blizzard 060, 1200's ide, latest sfs, scsi.device 40.12 atm, because the bb2 scsi update crashes the thing. This will be updated and patched soon enough. I reinstalled the system, after some misbehaving lha took out the system partition (this time) and i can now handle files larger then ram. But i had a weird issue where i couldnt place the first partition on the first cylinder.

[Framiga]

because there is the RDB there. (starting the first partition from cyl. 2 is better)

[mike-]

Framiga, aha thanks, that ha me very puzzled for a while.

i've now extracted, patched, and loaded the scsi.device, but check4gb still says >4g, no? is this because the partition isnt above 4gb? or because it cant take it? fixhddsize worked tho, thanks Thomas, your a genius.

For some strange reason however, i had to leave out the NOREBOOT part when loading the scsi.device. tried loadmodule before blizkick, stuffing the scsi.device in blizkick modules, and everything else i could think of. version scsi.device said 40.12 no matter what

[Thomas]

is this because the partition isnt above 4gb?

Yes. The column should actualy be "above 4GB", but there is only space for four letters in the head line. ">4gb" seemed to be the best abbrevation.

The only column which matters is "check". If it say ok, then it's ok.

Bye,
Thomas

[mike-]

Great, should be good then, experienced a speed up aswell, which is always welcome.

Different problem now however, loadmodule seems to nullify the setpatch amigaos rom update somewhat, version reports back 40.68 after loadmodule, but scsi.device 43.45. With NOREBOOT i get kick 45.47 and scsi 40.12.

Seems i have something to ponder tomorrow, all the os39-bb2 modules seem to be firmly stuck in there, except i cant run 3.9 apps, like finder. Easiest thing would probably be to stuff the patched scsi.device into the 3.1 kick image and continue passing the skipromupdates "Scsi.device"