Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
92 user(s) are online (49 user(s) are browsing Forums)

Members: 0
Guests: 92

more...

Headlines

Forum Index


Board index » All Posts (salass00)




Re: Multiview in July update ?
Just can't stay away
Just can't stay away


@Snuffy

Most likely a bug in simplehtml.datatype. Send a crash log to the author and maybe he will be able to fix it. After all he can't fix bugs he doesn't know about...

Why do you insist on using this datatype anyway? Considering how minimal the HTML support in it is.

You can change the default tool for html files (I have it set to AWeb here). Just open icon information, change default tool and then "Save As default html".

Go to top


Re: .hdf files (diskimage.device 52.x)
Just can't stay away
Just can't stay away


@joerg

Of course I would never hardcode such assumptions into the device! I'm not that stupid.

It's still a fact though that it returns the wrong dimensions in this case since it assumes the following:

BlockSize = 512
BlocksPerTrack = 1
Heads = 1
Cylinders = filesize / 512

So some way of letting the device know the correct BlocksPerTrack, Heads and BlockSize would be needed hence the command I propose above.

[edit]

Anyway you're idea for a tool for fixing the files sounds good since that would mean they would still be mountable the usual way. I think I'll go for that. Thanks.

[edit]

Done.


Edited by salass00 on 2007/8/3 22:52:04
Go to top


Re: .hdf files (diskimage.device 52.x)
Just can't stay away
Just can't stay away


@joerg

It worked . I could even mount the hardfile using "IDFO:" now.

Thanks a lot!

Still not a very ideal solution though. I'll have to think on this.

@all

Currently I'm thinking a command with a template like:

MountHardfile UNIT/K/N,FILE/A,DEVICENAME/K,BLOCKSPERTRACK/N,BLOCKSIZE/N,RESERVED/N,SURFACES/N

where all arguments except for file (and maybe unit and/or device name) are optional (sensible defaults will be used instead).

What do you people think?

Go to top


Re: .hdf files (diskimage.device 52.x)
Just can't stay away
Just can't stay away


@joerg

Thanks for the explanation. So I guess if I modified TD_GETGEOMETRY to return the correct size it would work also. I'll have to try this out.

Go to top


Re: .hdf files (diskimage.device 52.x)
Just can't stay away
Just can't stay away


@Raziel

I added some of the settings that were missing from my makefile but it didn't help any. Also tried with Reserved=1 (I used 2 with E-UAE though so that should be correct).

One interesting thing I noticed:

If I make a copy of the hardfile and then mount and format it the header looks very different.

Before:

00000000444F5303 00000000 00000000 00000000 DOS.............
0000001000000000 00000000 00000000 00000000 ................
0000002000000000 00000000 00000000 00000000 ................
0000003000000000 00000000 00000000 00000000 ................
0000004000000000 00000000 00000000 00000000 ................
0000005000000000 00000000 00000000 00000000 ................
0000006000000000 00000000 00000000 00000000 ................
0000007000000000 00000000 00000000 00000000 ................
00000080: 
00000000 00000000 00000000 00000000 ................
00000090: 
00000000 00000000 00000000 00000000 ................
000000A000000000 00000000 00000000 00000000 ................
000000B000000000 00000000 00000000 00000000 ................
000000C000000000 00000000 00000000 00000000 ................
000000D000000000 00000000 00000000 00000000 ................
000000E000000000 00000000 00000000 00000000 ................
000000F000000000 00000000 00000000 00000000 ................


After "quick format":

00000000444F5303 3B672C85 416D6967 61205061 DOS.;g,.Amiga Pa
00000010
72746974 696F6E3A 20536563 746F7253 rtitionSectorS
00000020
697A653D 35313220 53757266 61636573 ize=512 Surfaces
00000030
3D312053 6563746F 72735065 72426C6F =1 SectorsPerBlo
00000040
636B3D31 20536563 746F7273 50657254 ck=1 SectorsPerT
00000050
7261636B 3D312052 65736572 7665643D rack=1 Reserved=
0000006032205072 65416C6C 6F633D30 204C6F77 2 PreAlloc=0 Low
00000070
43796C3D 30204869 67684379 6C3D3132 Cyl=0 HighCyl=12
00000080: 34393939 20426F6F 74507269 3D302044 4999 BootPri=0 D
00000090: 6F735479 70653D30 78343434 46353330 osType=0x444F530
000000A0
30204E61 6D653D49 48443020 44617465 0 Name=IHD0 Date
000000B0
3D323030 372D3038 2D303300 00000000 =2007-08-03.....
000000C000000000 00000000 00000000 00000000 ................
000000D000000000 00000000 00000000 00000000 ................
000000E000000000 00000000 00000000 00000000 ................
000000F000000000 00000000 00000000 00000000 ................

Go to top


Re: .hdf files (diskimage.device 52.x)
Just can't stay away
Just can't stay away


@LiveForIt

You're thinking of BlockSize. BlocksPerTrack is usually 32 for harddisk partitions. It is also the same setting as I use in the E-UAE config file.

I've tried explicitly setting BlockSize to 512 but it didn't help any.

Go to top


.hdf files (diskimage.device 52.x) [solved]
Just can't stay away
Just can't stay away


I've been trying to mount the gcc.hdf hardfile with diskimage.device using the following mountlist (it's a partition hardfile not a RDB one):

Quote:

Priority = 10
StackSize = 4096
GlobVec = 0
Surfaces = 1
BlocksPerTrack = 32
Reserved = 2
LowCyl = 0
HighCyl = 3905
Buffers = 50
BufMemType = 0
MaxTransfer = 0x7FFFFFFE
Mask = 0xFFFFFFFE
DosType = 0x444F5300


Also tried using:
Quote:

DosType = 0x444F5303

but it didn't help.

Most of the above is grabbed using Makemountlist in E-UAE so should be correct (LoCyl/HighCyl, etc.).

Does the TD_GETGEOMETRY implementation in diskimage.device matter at all in this case? I tried leaving the REMOVABLE flag unset but it didn't help any.

I can't understand why it isn't working...

Or could it be because I am first mounting the device and then "inserting" the disk? Doesn't seem like it to me though since the disk does show up, just that it shows up as "IHDO:Uninitialized" and can't be accessed...

Any help with getting this working would be appreciated.


Edited by salass00 on 2007/8/3 22:52:41
Go to top


Re: AOS4.0 UPtime ShowDOWN
Just can't stay away
Just can't stay away


@Atheist

No big up times from me because I've been developing diskimage.device lately and have to do a reboot every now and then to test a new version (not because of crashes or anything like that).

Also I can't sleep with the computer on.

Go to top


Re: CPUTemp.docky and the CPU usage graph
Just can't stay away
Just can't stay away


@dwolfman

That's because you have only added the dnetc GUI task, which spends most of it's time sleeping and not using any CPU.

What you need to do is add the dnetc crunch task. To find out its name you can use either Ranger or Scout programs. In Ranger it's listed as a childtask of "dnetc" so should be easy enough to find.

Go to top


Re: Version AISS
Just can't stay away
Just can't stay away


@Mason

Also stick to a standard format for the versions so that programs can easily check for if it's a >= version. I suggest using the standard version.revision format where revision is >= 1 (i.e. "3.2" for version 3, 2nd revision).

This should be quite easy for a program to parse to obtain the version and revision and then check that it's new enough. Just split them up by replacing the '.' with '\0' and then use StringToLong() or atol() to convert the strings to numbers.

Go to top


Re: Spot's porting CHALLENGE!
Just can't stay away
Just can't stay away


@jabirulo

If you're using the latest SDL_mixer from OS4Depot make sure you also install the latest SDL (v1.2.11) from:

http://www.rcdrummond.net/sdl/index.html

It is stated as a requirement in the readme.

Go to top


Re: OS4 doesn't boot (black screen) - SOLVED
Just can't stay away
Just can't stay away


@AmiKit

Quote:

I can't believe it.
It seems the problem was in AddNetInterface command in startup-sequence. I added RUN inf front of the command and everything is fine now. I wonder why there's no RUN by default?


Because you might have programs in user-startup (f.e. smbfs) or in WBStartup that require a network connection to be available on startup.

The solution I use here is to have a separate network-startup in S: containing the AddNetInterface and smbfs commands that I execute using "Run <>NIL: Execute S:network-startup".

Go to top


Re: No more ports with dodgy documentation!
Just can't stay away
Just can't stay away


@Chris

Good work!

I've already used it on the documentation for my dvdauthor port.

Go to top


Re: Fkey cannot save prefs
Just can't stay away
Just can't stay away


@COBRA

Quote:

Actually, there's nothing stopping a program from loading its icon's tooltypes even when started from shell.


There's nothing stopping it. Except that this happens to be the way that commodities should work according to Commodore, it is stated so f.e. in the RKRM: Libraries section on commodities.library.

Also the commodities helper functions for reading tooltypes/arguments (ArgArrayInit(), ArgString(), etc.) work this way.

To be honest I really don't think this behavior makes much sense though.

Go to top


Re: Fkey cannot save prefs
Just can't stay away
Just can't stay away


@LiveForIt

Quote:

A normal AmigaDOS program will read it argumenst like this

Int Main (int args, char **arg )
{
For (i=<args;i++)
Printf(?arg%i : %s\n ?,I Arg[i] );
}


A normal AmigaDOS (OS >= 2.0) program will use IDOS->ReadArgs(). This is what all the OS C: commands use for their commandline args. It takes care of the "?" option as well as providing a standard way to supply commandline arguments.

This argc, argv thing is an ANSI C construct and is provided by the C startup code and has nothing to do with the AmigaDOS. AmigaDOS just passes the entire commandline as a long string that the program can then parse as it pleases.

Quote:

And also if you start the program from AmigaDOS you most take care and make shore it starts from the same directory as your icon, unless you change directory to your tooltype icon in your program.


Not if the program makes use of "PROGDIR:".

Go to top


Re: Small update to FliteGUI - new v1.2
Just can't stay away
Just can't stay away



Go to top


Re: Small update to FliteGUI - new v1.2
Just can't stay away
Just can't stay away


@Elwood

Make sure that you have:

AUDIO in DEVS:DOSDrivers/
AHI-Handler in L:

Also which version of AHI-Handler (m68k or PPC)? I have tested with both and have no problems with either of them though.

Also check that AHI unit 0 is correctly set up in AHI prefs.

Have you tried running flite from the commandline (without the GUI)?

flite -t "insert text here"

I have looked at the crash log you sent me by e-mail but as the crash doesn't happen in either of the flite exes or ahi-handler it doesn't help much in narrowing down the problem.

Quote:

Stack trace:
native kernel module kernel.debug+0x0001a2b0
native kernel module kernel.debug+0x0002df90
native kernel module kernel.debug+0x0002f2f0
native kernel module kernel.debug+0x00074a0c


Possibly one of the programs (flite?) is trashing some critical memory somewhere and this then later shows up as a kernel crash in Grim Reaper. Unfortunately this tells absolutely nothing about what code is actually causing the crash though.

Go to top


Re: What's happened to Smart FileSystem 2?
Just can't stay away
Just can't stay away


@joerg

Quote:

I've tested it successfully with a 4,546,701,312 bytes image file.


Thanks.

Quote:

You can remove everything after the StackSize line from CD1 and CD2, the "Control" options in these mountlists are only supported by CacheCDFS and are ignored by CDFileSystem.

You should use different names for the diskimage.device mountlists, if someone has 2 CD/DVD drives installed he has a CD1: already, and on classic Amigas at least DF0: is always there (unless the floppy drive is broken).


Done.

Quote:

An icon for DiskImageGUI should be included, even if it's just the def_tool one, if you put it into SYS:WBStartup without icon it's not started.


That was a mistake. There should have been an icon, except I forgot to include it in all three releases I've made up to now. The icon I'm using is the def_disk one.

Thanks for pointing it out. I probably wouldn't have noticed it otherwise.

Go to top


Re: What's happened to Smart FileSystem 2?
Just can't stay away
Just can't stay away


@joerg

Quote:

NSD64 is only half of what you need, the image file has to be accessed using 64 bit offsets as well. OS4 final includes the 64 bit dos.library functions, but IIRC they were not in the last public SDK yet.


This is the function I am using (from latest public SDK):

success = ChangeFilePosition( file, position, mode )
int32 ChangeFilePosition(BPTR, int64, int32)

Quote:

I have another file system with 100% working large file support, if you sent me a beta version of diskimage.device I can test if it works correctly with files > 4 GB.


The latest v52.3 version I uploaded to OS4Depot today should have working NSD64 support. If you could try it out with your filesystem it would be appreciated.

Quote:

IIRC the ICD0 mountlist included in the old, m68k versions of diskimage.device is ok (a lot of it is for CacheCDFS, but it's ignored by CDFileSystem and doesn't cause problems). You just have to make sure it includes DosType = 0x43443031, LowCyl = 0 and BlockSize = 2048.


Thanks for that. I'll try it out if I can find/make some smaller DVD iso files to test with.

Go to top


Re: What's happened to Smart FileSystem 2?
Just can't stay away
Just can't stay away


@salass00

Screenshot showing a new feature that will be in the 52.3 release of diskimage.device (write protection):

Resized Image

Go to top



TopTop
« 1 ... 82 83 84 (85) 86 87 88 ... 91 »




Powered by XOOPS 2.0 © 2001-2023 The XOOPS Project