Maybe the drivers [are the probblem], the graphics card works perfectly with booted DOS 7.
Perhaps the manufacturer of your graphics card has an updated set of drivers for Windows operating systems. ----------------------------
Did this happen with: textsafe=save in sstools.ini?
Yes, it does not help in my case.
Its surprising that textsafe=save doesn't work because textsafe=save "tells Fractint to save/restore the entire image. Expanded or extended memory is used for the save if you have enough available..." It looks like your graphics card drivers are not implementing the image save and restore correctly. Maybe the manufacturer of your graphics card has an updated set of drivers for Windows operating systems. --------------------------
and the monitor reawakens
If by "monitor reawakens" you mean that you let the power management timer routine dim the brightness of your monitor after a specified period of time, I also get bad pixels in Fractint when my monitor powers down automatically. To prevent this while running fractint I tell the Power Management routine (the icon is a picture of a gray battery behind a gray electrical plug) to no longer dim my monitor. (Set "Turn off Monitor" to "Never" and click OK). When I am no longer using Fractint I turn the automatic monitor power down feature ("Turn off Monitor") back to "5 minutes". Since the monitor never dims while I am viewing an image being calculated, I never get bad pixels from the monitor being powered off and on. ----------------------------- You probably want to use your computer to do other things while an image is being calculated -- as I do. Here is what I do: I use a Win98 screen resolution of 1280 x 1024. (The exact resolution is not important.) I use the Fractint View Window <v> option "Preview Display" set to "yes" and an "Auto Window Size Reduction Factor" of 4 (6 for very slow images) to quickly find the image I want to calculate. Calculating these small images using Fractint's View Window speeds up calculating an image while looking for a pleasing image. If it will take a long time to calculate the final full resolution image (with "Preview Display" set to "no"), I use a Disk Video mode to start the calculation. Since the "Disk Video is in progress" screen is a text screen I can type <alt><enter>. This changes the Fractint program to a window on the Win98 desktop and I can use my computer for other tasks while the image is being calculated. I have even had multiple instances of Fractint running at the same time in Disk Video mode in Win98 windows. They seemed to share the CPU cycles approximately equally. I don't get too bad a slowdown of the other Win98 tasks I do while Fractint is running windowed in Disk Video mode even though my CPU is only 400 MHz. -------------------------- By the way, to return to full screen Fractint -- to save the image calculated in Disk Video mode -- after selecting the windowed DOS Fractint text window with <alt><tab> I use <alt><enter> to maximize the window to full screen. <alt><tab> is only used to *select* windows on my -- system, it does not to change their size. <alt><enter> is used to change a program from windowed to full screen or full screen to windowed. If using <alt><tab> to select the Fractint window also changes its size to full screen on your system, it could be that the default window size for your DOS session window is full screen instead of windowed. This can be changed in the properties of the link or icon used to run the DOS session window. So that I didn't have to permanently change my DOS session icon's window properties I created an icon to run Fractint. To create the icon on my task bar I "right dragged" FRACTINT.EXE to the my task bar and released the right mouse button and then chose "Create shortcut(s) here". On the icon's Properties (right click the icon) "Screen" tab I set its default window size to "Full Screen". I also have "Display toolbar", "Restore settings on Startup" and "Fast ROM emulation" checked. On the "Memory" tab I have the Memory settings set as all "Auto". On the "Misc" tab "Allow screen saver" is unchecked. And "Idle sensitivity" is set to "High". "Always suspend" is unchecked -- this is very important! If you don't uncheck this box Fractint will not get any CPU cycles when it is windowed. On the "Program" tab, "Run" is set to "Maximized" and "Close on exit" is checked. ------------------------------- I have just realized that when you say:
a restored image is destroyed, partly overwritten by the text you may be using the word "restore" to refer to when you undim your monitor. I had assumed that you were referring to images restored using Fractint's "restore image" function that you get to by typing the <r> key.
Are you using the word "restore" to refer to when you power your monitor back on? <---<< ------------------------------- Please let me know if not letting your monitor dim stops this form of pixel corruption in Fractint. - Hal Lane ######################### # hallane@earthlink.net <mailto:hallane@earthlink.net> # #########################
-----Original Message----- From: Albrecht Niekamp [mailto:Albrecht.niekamp@t-online.de] Sent: Saturday, September 10, 2005 5:57 AM To: Hal Lane Subject: Re: textsafe=save in sstools.ini "...should work on all adapters in all modes..."
----- Original Message ----- From: "Hal Lane" <hallane@earthlink.net> To: "Philofractal" <philofractal@lists.fractalus.com>; "Fractint_msg" <fractint@mailman.xmission.com>; <Albrecht.niekamp@t-online.de> Sent: Saturday, September 10, 2005 1:39 AM Subject: textsafe=save in sstools.ini "...should work on all adapters in all modes..."
Did this happen with: textsafe=save in sstools.ini?
Yes, it does not helpin my case. Only if Fractint is started from a " windowed" DOS Commander I have text and image, but even then a restored image is destroyed, partly overwritten by the text.
I use textsafe=save on my vanilla Gateway 400MHz Pentium II under Win98 and I don't lose restored images when I switch to a text screen and back -- and the speed is OK.
-----------------------------------------------------------
The textwindow can be called by the cool switch and the monitor reawakens, but the image is gone.
What are you referring to by the phrase "cool switch"?
Alt_tab>
----------------------------------------------------------- These problems are almost certainly related to your graphics card and/or its drivers. Maybe the drivers, the graphics card works perfectly with booted DOS 7. The WIN98 "Real DOS" performance is not acceptable, calculation time increases 3 or 4 times. As a last resort: I note that nick.grasso@nasrecruitment.com writes:
"You could try buying a new video card. Be sure to get one that supports the old DOS VESA modes. The old Matrox cards used to be good."
------------------------------------------------------------
-- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.10.21/96 - Release Date: 9/10/05