I built a computer last year using an Athlon with a Gigabyte motherboard. I had troubles with Fractint - with any SVGA mode the computer would hang after the completion of the image. I always assumed this was an Windows XP issue. Today I tried Fractint with freedos on the same computer, with the same results. So apparently it's an incompatability bgetween fractint and my compuiter. Truecolor, 320x200, diskvideo, and even tweaked modes work. SCGA modes fail, and only after the image completes. This behavior appears to have nothing to do with recent versions. Has anyone else had trouble with Athlon? Hmm, maybe I need to look at bios settings. Tim
Tim,
I built a computer last year using an Athlon with a Gigabyte motherboard. I had troubles with Fractint - with any SVGA mode the computer would hang after the completion of the image. I always assumed this was an Windows XP issue.
Today I tried Fractint with freedos on the same computer, with the same results. So apparently it's an incompatability bgetween fractint and my compuiter. Truecolor, 320x200, diskvideo, and even tweaked modes work. SCGA modes fail, and only after the image completes.
This behavior appears to have nothing to do with recent versions.
Has anyone else had trouble with Athlon?
I just built a 2.4 GHz Celeron. It has an Intel motherboard with built in video. Fractint works fine under Win98, but under WinXP it has problems. At higher resolutions, no image appears on the screen. But, if you save the non-image and look at it with a graphics file viewer, it looks just fine. I've been through all the XP compatibility settings with no improvement. The makefcfg routine returns all the applicable video modes and Fractint recognizes that these modes are available. One possible cause could be that we might be discarding the upper portion of the video address returned by the VESA video functions. This was all after I updated the XP video drivers for this board. Before the update, Fractint produced a garbled screen image in these video modes. Try updating the video drivers for XP.
Hmm, maybe I need to look at bios settings.
Bios settings should have no effect. Jonathan
Jonathan wrote:
Try updating the video drivers for XP.
I guess I didn't make it clear. I booted the machine to Freedos, an open source DOS clone, and got the exact same behavior. Therefore Win XP has nothing to do with it. Since it works OK in some video modes, but not others, there must be some video logic that is messing me up. Only SVGA has the problem. And as I said, the image is generated OK, so it is something in the logic that cleans up after the image is produced. I'll try to narrow down exactly where it hangs.
Bios settings should have no effect.
I wonder if there's an interrupt that is not set right. Most are set to auto. I realize you can't debug this at a distance. I'll see what I can come up with. BTW, Freedos can be set up to boot from a CD. This is a very promising way of extending the life of the DOS version. All that's necessary is to have a FAT partition to save images. Tim
On Monday 31 May 2004 9:52 pm, Tim Wegner wrote:
I guess I didn't make it clear. I booted the machine to Freedos, an open source DOS clone, and got the exact same behavior. Therefore Win XP has nothing to do with it.
Uhm, I knew that. Is the video integrated with the motherboard? Is it possible there is a video bios update? Jonathan
Tim Wegner wrote:
BTW, Freedos can be set up to boot from a CD. This is a very promising way of extending the life of the DOS version. All that's necessary is to have a FAT partition to save images.
No need to actually have the FAT partition, since I have been saving the GIF files onto a NTFS formatted drive without any problems. Several of the posted FOTD images were generated on a Windows XP system and saved to the NTFS drive. Then uploaded directly from there to my domain for inclusion in the webpages. Sincerely, P.N.L. ------------------------------------------------- http://home.att.net/~Paul.N.Lee/PNL_Fractals.html http://www.Nahee.com/Fractals/
On Tuesday 01 June 2004 1:08 am, Paul N. Lee wrote:
No need to actually have the FAT partition, since I have been saving the GIF files onto a NTFS formatted drive without any problems.
It is true that Fractint has no problem with NTFS, but Win98 doesn't recognize it. At least, not on my machine. Jonathan
Jonathan Osuch wrote:
Paul N. Lee wrote:
No need to actually have the FAT partition, since I have been saving the GIF files onto a NTFS formatted drive without any problems.
It is true that Fractint has no problem with NTFS, but Win98 doesn't recognize it.
Also true, but from Tim's initial posting (and following one) on this topic, I assumed the conversation was more geared to FractInt running in a Windows XP environment and not displaying images correctly. This is the first mention of the Win-98 OS for this topic (unless there have been private ones). But I do see that FAT might be necessary for the standalone DOS boot. Sincerely, P.N.L. ------------------------------------------------- http://home.att.net/~Paul.N.Lee/PNL_Fractals.html http://www.Nahee.com/Fractals/
Paul wrote:
Also true, but from Tim's initial posting (and following one) on this topic, I assumed the conversation was more geared to FractInt running in a Windows XP environment and not displaying images correctly. This is the first mention of the Win-98 OS for this topic (unless there have been private ones).
But I do see that FAT might be necessary for the standalone DOS boot.
Exactly. My initial post was confusing. We could easily distribute Fractint as an ISO file for a freedos-bootable CD. To make this work you would need a FAT or FAT32 partition on the computer top save images. This might be daunting for beginners, but for others it's simple. Kinda brings back memories to run DOS on my new PC :-) Everybody should understand that the Athlon is not necessarily the culprit on my new PC. I have had zero problems with this PC for any other purpose, including running Windows XP and numerous flavors of Linux. I will try to debug the problem. It may be video-related. I could try swapping out the video card and see what happens. The video card uses AGP, which, of course, Fractint never dreamed of ... Tim
Hi Tim and Fractrint Friends, A client of mine has been experimenting with a 64 bit version of LINUX and is wondering if there has been a version of XFractint compiled under a 64 bit environment. Has this been done? Is it being considered for a future release? Please advise, Many thanks, Paul. ---------------------------------------------------------- Paul de Leeuw Computers NSW Central Coast, Australia Email: pdeleeuw@deleeuw.com.au www: < http://www.deleeuw.com.au> ABN 72 360 822 562 ----------------------------------------------------------
Paul asked:
A client of mine has been experimenting with a 64 bit version of LINUX and is wondering if there has been a version of XFractint compiled under a 64 bit environment. Has this been done? Is it being considered for a future release?
Anyone with the appropriate target environment could try. Neither Jonathan (as far as I know) nor I have a 64 bit machine yet. It should just be a matter of taking account of long being 64 bits instead of 32 bits. It's hard to know in advance how pervasive the changes would be.
From it's roots as a DOS medium memory model application, I'm sceptical that there's anything about 64 bit Linux that would benefit xfractint without a major rewrite - but then it would be a different program.
Tim
Hello, I've just managed to build Xfractint using the tarball xfractint-20.04p03.tar.gz downloaded from http://www.fractint.org/ftp/current/linux/ on a Linux Fedora Core 4 x86_64 install running on a Dell PowerEdge SC420 server which has an Intel Celeron D processor supporting EM64T i.e. 64-bit linux on a 64-bit machine. I had to edit the makefile a little, changing the "-mcpu=pentium" to "-mtune=nocona" and changing -usr/X11R6/lib in the LIBS define to /usr/X11R6/lib64. Once built, it at least runs and gives me the default mandelbrot, and I can get into the menus and change the type to Julia and draw it. Haven't tested it any further. Not sure about speed as I only ever use the PC version of fractint! Iain.
-----Original Message----- From: fractdev-bounces+iain_stirling=btinternet.com@mailman.xmission .com [mailto:fractdev-bounces+iain_stirling=btinternet.com@mailman. xmission.com] On Behalf Of Tim Wegner Sent: 01 October 2005 15:39 To: Fractdev@mailman.xmission.com Subject: Re: [Fractdev] 64 Bit version of Fractint
Paul asked:
A client of mine has been experimenting with a 64 bit version of LINUX and is wondering if there has been a version of XFractint compiled under a 64 bit environment. Has this been done? Is it being considered for a future release?
Anyone with the appropriate target environment could try. Neither Jonathan (as far as I know) nor I have a 64 bit machine yet.
It should just be a matter of taking account of long being 64 bits instead of 32 bits. It's hard to know in advance how pervasive the changes would be.
From it's roots as a DOS medium memory model application, I'm sceptical that there's anything about 64 bit Linux that would benefit xfractint without a major rewrite - but then it would be a different program.
Tim
_______________________________________________ Fractdev mailing list Fractdev@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/fractdev
-- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.11.9/115 - Release Date: 29/09/2005
-- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.11.9/115 - Release Date: 29/09/2005
Hi Tim and Iain, Many thanks for your quick replies. I'll contact my client and see where he wants to go with this. I'll report any progress. Thanks, Paul. ---------------------------------------------------------- Paul de Leeuw Computers NSW Central Coast, Australia Email: pdeleeuw@deleeuw.com.au www: < http://www.deleeuw.com.au> ABN 72 360 822 562 ---------------------------------------------------------- -----Original Message----- From: fractdev-bounces+pdeleeuw=telstra.com@mailman.xmission.com [mailto:fractdev-bounces+pdeleeuw=telstra.com@mailman.xmission.com] On Behalf Of Iain Stirling Sent: Sunday, 2 October 2005 12:33 AM To: 'Fractint developer's list' Subject: RE: [Fractdev] 64 Bit version of Fractint Hello, I've just managed to build Xfractint using the tarball xfractint-20.04p03.tar.gz downloaded from http://www.fractint.org/ftp/current/linux/ on a Linux Fedora Core 4 x86_64 install running on a Dell PowerEdge SC420 server which has an Intel Celeron D processor supporting EM64T i.e. 64-bit linux on a 64-bit machine. I had to edit the makefile a little, changing the "-mcpu=pentium" to "-mtune=nocona" and changing -usr/X11R6/lib in the LIBS define to /usr/X11R6/lib64. Once built, it at least runs and gives me the default mandelbrot, and I can get into the menus and change the type to Julia and draw it. Haven't tested it any further. Not sure about speed as I only ever use the PC version of fractint! Iain. *************************************************** -----Original Message----- From: fractdev-bounces+pdeleeuw=telstra.com@mailman.xmission.com [mailto:fractdev-bounces+pdeleeuw=telstra.com@mailman.xmission.com] On Behalf Of Tim Wegner Sent: Sunday, 2 October 2005 12:39 AM To: Fractdev@mailman.xmission.com Subject: Re: [Fractdev] 64 Bit version of Fractint Paul asked:
A client of mine has been experimenting with a 64 bit version of LINUX and is wondering if there has been a version of XFractint compiled under a 64 bit environment. Has this been done? Is it being considered for a future release?
Anyone with the appropriate target environment could try. Neither Jonathan (as far as I know) nor I have a 64 bit machine yet. It should just be a matter of taking account of long being 64 bits instead of 32 bits. It's hard to know in advance how pervasive the changes would be.
From it's roots as a DOS medium memory model application, I'm sceptical that there's anything about 64 bit Linux that would benefit xfractint without a major rewrite - but then it would be a different program.
Tim
-----Original Message----- From: fractdev-bounces+iain_stirling=btinternet.com@mailman.xmission .com [mailto:fractdev-bounces+iain_stirling=btinternet.com@mailman. xmission.com] On Behalf Of Tim Wegner Sent: 01 October 2005 15:39 To: Fractdev@mailman.xmission.com Subject: Re: [Fractdev] 64 Bit version of Fractint
Paul asked:
A client of mine has been experimenting with a 64 bit version of LINUX and is wondering if there has been a version of XFractint compiled under a 64 bit environment. Has this been done? Is it being considered for a future release?
Anyone with the appropriate target environment could try. Neither Jonathan (as far as I know) nor I have a 64 bit machine yet.
It should just be a matter of taking account of long being 64 bits instead of 32 bits. It's hard to know in advance how pervasive the changes would be.
From it's roots as a DOS medium memory model application, I'm sceptical that there's anything about 64 bit Linux that would benefit xfractint without a major rewrite - but then it would be a different program.
Tim
_______________________________________________ Fractdev mailing list Fractdev@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/fractdev
-- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.11.9/115 - Release Date: 29/09/2005
-- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.11.9/115 - Release Date: 29/09/2005 _______________________________________________ Fractdev mailing list Fractdev@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/fractdev
Tim,
A client of mine has been experimenting with a 64 bit version of LINUX and is wondering if there has been a version of XFractint compiled under a 64 bit environment. Has this been done? Is it being considered for a future release?
Anyone with the appropriate target environment could try. Neither Jonathan (as far as I know) nor I have a 64 bit machine yet.
I got a new laptop last weekend with a 64 bit Athlon cpu. I'll be installing a 64 bit OS today, then we'll see. BTW, under XP, Fractint works on this machine. There are some glitches on the <v> screen, but I can view resolutions up to 1024x768. It has an ATI Mobile Radion X600 graphics chip. This machine has enough disk space so that I will be able to install the MS SDK and hopefully compile Winfract.
It should just be a matter of taking account of long being 64 bits instead of 32 bits. It's hard to know in advance how pervasive the changes would be.
From it's roots as a DOS medium memory model application, I'm sceptical that there's anything about 64 bit Linux that would benefit xfractint without a major rewrite - but then it would be a different program.
Switching over to wxWidgets might be a good excuse to do that. Jonathan
Jonathan wrote:
I got a new laptop last weekend with a 64 bit Athlon cpu. I'll be installing a 64 bit OS today, then we'll see.
Neat! I have yet to bite on 64 bits, but it shouldn't be too long. Maybe dual core?
BTW, under XP, Fractint works on this machine. There are some glitches on the <v> screen, but I can view resolutions up to 1024x768. It has an ATI Mobile Radion X600 graphics chip.
Is that 32 bits or 64 bits windows? Either way, I'm grateful it works at all. ATI doesn't have the best VESA support.
Switching over to wxWidgets might be a good excuse to do that.
Amen. BTW, if you look up Fractint in wikipedia, it credits fractint as being one of the oldest open source projects still being maintained - that's amazing. Which reminds me to say, I haven't forgotten my commitment to finish up the Fractint docs, at least the scrolling screen and possibly more. Life is very full, but I will make time. Tim
Tim,
I got a new laptop last weekend with a 64 bit Athlon cpu. I'll be installing a 64 bit OS today, then we'll see.
Neat! I have yet to bite on 64 bits, but it shouldn't be too long. Maybe dual core?
Perhaps for my next desktop machine. Xfractint compiles with a couple of minor changes in the make file. There are the expected warnings about different integer sizes, but it runs as-is.
BTW, under XP, Fractint works on this machine. There are some glitches on the <v> screen, but I can view resolutions up to 1024x768. It has an ATI Mobile Radion X600 graphics chip.
Is that 32 bits or 64 bits windows? Either way, I'm grateful it works at all. ATI doesn't have the best VESA support.
I don't know for sure. I was under the impression that it is 32-bit. Jonathan
Hi all again, nice it's still not all dead here! Jonathan wrote:
Xfractint compiles with a couple of minor changes in the make file. There are the expected warnings about different integer sizes, but it runs as-is.
As-was, I wasn't even able to compile help.src, got too much of: "Warning help.src 16: Hot-link destination is not in the document." (Making hc itself gave me a few warnings about cast from pointer to integer of different size, caused by CHK_BUFFER macro.) So I made hc tolerant by MAX_WARNINGS = 0, to get helpdefs.h at all. Then, make xfractint was able to continue up to the final gcc -o xfractint, but here ld fails with: "i386 arch. of input calmanfx.o is incompatible with i386:x86-64 output" Though I tried some tweaks here and there, no success so far. Could anyone of you please give me an insight on what's wrong? I have openSuse / AMD64x2 / gcc4.2.1 / nasm 0.98.39 / xfractint 20.04p08. Scott Boyd's xfractint 20.02.4 binary runs fine. Thanks in advance for any pointers! /Charlie/
Charlie,
Xfractint compiles with a couple of minor changes in the make file. There are the expected warnings about different integer sizes, but it runs as-is.
As-was, I wasn't even able to compile help.src, got too much of: "Warning help.src 16: Hot-link destination is not in the document."
(Making hc itself gave me a few warnings about cast from pointer to integer of different size, caused by CHK_BUFFER macro.)
I don't have any idea what might cause this. I did notice the make file needs some tweaking if the file fractint.hlp already exists and changes are made to the *.src files, which should force a recompile of fractint.hlp, but doesn't. I'll have to take a look at how hc compliles.
So I made hc tolerant by MAX_WARNINGS = 0, to get helpdefs.h at all. Then, make xfractint was able to continue up to the final gcc -o xfractint, but here ld fails with: "i386 arch. of input calmanfx.o is incompatible with i386:x86-64 output"
Don't use nasm, or the pre-compiled assembly version of calmanfx. I haven't worked with those for some time. I would guess that the assembly code is working with 32-bit chunks of data, not 64-bit. So, the interface to the C code would be slightly different.
Though I tried some tweaks here and there, no success so far. Could anyone of you please give me an insight on what's wrong?
I have openSuse / AMD64x2 / gcc4.2.1 / nasm 0.98.39 / xfractint 20.04p08. Scott Boyd's xfractint 20.02.4 binary runs fine.
I am using gcc version 4.2.3. Jonathan
Jonathan Osuch wrote:
Fractint works fine under Win98, but under WinXP it has problems. At higher resolutions, no image appears on the screen. But, if you save the non-image and look at it with a graphics file viewer, it looks just fine.
Yes, this is pretty much the same thing I mentioned on the FractInt Discussion List back around April 16th. I have a Dell machine that creates higher resolution FractInt images under Windows XP. The only difference is that there is something generated on the screen, it is just an altered version of the actual fractal graphic. As if it is trying to format a 800x600 image onto a 1024x768 monitor, where part of one line is used to finish the previous one, and then finishes by wrapping to the next line. But the saved image displays correctly with any graphic editor/viewer. Sincerely, P.N.L. ------------------------------------------------- http://home.att.net/~Paul.N.Lee/PNL_Fractals.html http://www.Nahee.com/Fractals/
Tim Wegner wrote:
Has anyone else had trouble with Athlon?
One of the companies that I contract for had gotten several awhile ago. And they experienced problems with the Athlons which was not happening with the Intel machines. Technical Support would load all new machines with the same configuration before being setup at the User's workstation. Since only the Athlons were having the problems they discontinued purchasing them. Sincerely, P.N.L. ------------------------------------------------- http://home.att.net/~Paul.N.Lee/PNL_Fractals.html http://www.Nahee.com/Fractals/
participants (7)
-
charlie chernohorsky -
Iain Stirling -
jonathan -
Jonathan Osuch
-
Paul -
Paul N. Lee -
Tim Wegner